[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Naming guidelines question



On Fri, 2006-05-26 at 13:55 -0400, Jesse Keating wrote:
> On Fri, 2006-05-26 at 20:42 +0300, Ville Skyttä wrote:
> > Do we expect users to browse into the upstream tarball distribution dirs
> > and select the name of a tarball without the version etc and paste it to
> > their command line (assuming that's what the above means)?  Or select it
> > from other documentation where the app/project name is very likely to be
> > spelled in different case than in the tarball?  And how about the rest
> > of the guidelines which say that certain packages must be prefixed eg.
> > by perl-*, python-*, or be named like $appname-$plugin?  What about
> > subpackages?
> 
> Not just browsing tarballs, but documentation that says 'You need
> PackageFoo' installed, or "You need ORBit2 to be able to use this,
> please install it through your vendor".  So the only way I would find
> acceptable a 'lowercase always' rule is if in each case we are breaking
> the upstream name we must have a Provides: UpstreamName .

This argument applies everytime we change the name from the upstream
provided one. We do that in many cases already. I dont see how this
applies only to case sensitivity but not to other renames. 

Rahul


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]