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

Re: Naming guidelines question



On Fri, 2006-05-26 at 12:54 -0400, Jesse Keating wrote:
> On Fri, 2006-05-26 at 21:30 +0530, Rahul Sundaram wrote:
> > Do we expect users to notice the specific case of the upstream projects
> > in webpages, documentation and type it correctly in yum everytime?
> > 
> 
> select -> insert

Is that really a goal worth pursuing?

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?

> _if_ we were ever to make package guidelines be lowercase only, we
> would need to modify rpm, yum, etc... to accept caps and pass them as
> lower case.

As long as the filesystems, rest of the tools in the OS, URLs etc in use
are case sensitive, I'm afraid that would not work too well in practice.
All lowercase would not solve anywhere near all problems either (see
above for some examples), but it would be a much less intrusive way to
avoid some of them than the above suggestions, and would be easy to
communicate/document.


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