[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [Fedora-packaging] Packaging/NamingGuidelines python modules naming
- From: Ville Skyttä <ville skytta iki fi>
- To: Discussion of RPM packaging standards and practices for Fedora <fedora-packaging redhat com>
- Subject: Re: [Fedora-packaging] Packaging/NamingGuidelines python modules naming
- Date: Thu, 6 Sep 2007 19:43:57 +0300
On Thursday 06 September 2007, Tom "spot" Callaway wrote:
> On Thu, 2007-09-06 at 16:32 +0200, Till Maas wrote:
> > Aloas,
> >
> > http://fedoraproject.org/wiki/Packaging/NamingGuidelines#head-8756a3bce65
> >2c376d7ba3908461b638784b6952d
> >
> > states:
> > | There is an exception to this rule. If the upstream source has "py"
> > | (or "Py") in its name, you can use that name for the package.
> >
> > Maybe there should be another exception when upstream includes python it
> > its name, e.g. fuse-python[1]. Should this be packaged as python-fuse or
> > can it stay with upstream's name fuse-python? Should it provide
> > python-fuse in case it stays with its upstream name?
>
> Does fuse-python have "py" in its name? If so, you can use that name for
> the package. ;)
I would personally call it python-fuse anyway for consistency, and perhaps
add "Provides: fuse-python = VR", but maybe that's just me.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]