[gentoo-dev] policy on case [in]sEnsiTiViTy to ebuild names

[gentoo-dev] policy on case [in]sEnsiTiViTy to ebuild names

[Christian Parpart]

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

Hi all,

I recently came into an issue of the ebuild names. usually I 
write them all lower case (that is: as-is), but recently, I 
run into packages to be submittet, that HavE different cAsEs. 
Namely the freedesktop's xlibs and xserver.

In xlibs, there're packages called libXcomposite, libX11 etc..
I'd like to preserve the case in portage, too since doing 
everything in lowercase doesn't really enheance readability 
overall, and we already have (especially on dev-perl) packages
that also have upper-cases anyway.

So, what's the policy on it?

Thanks in advance,
Christian Parpart.

-- 
http://www.winterschur.de/?fey <-- get sheeped!
Netiquette: http://www.ietf.org/rfc/rfc1855.txt
 00:44:27 up 27 days, 17:14,  1 user,  load average: 0.43, 0.47, 0.51

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

Re: [gentoo-dev] policy on case [in]sEnsiTiViTy to ebuild names

[Ciaran McCreesh]

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

On Fri, 26 Nov 2004 00:49:25 +0100 Christian Parpart <trapni@gentoo.org>
wrote:
| I recently came into an issue of the ebuild names. usually I 
| write them all lower case (that is: as-is), but recently, I 
| run into packages to be submittet, that HavE different cAsEs. 
| Namely the freedesktop's xlibs and xserver.
<snip>
| So, what's the policy on it?

In general, use lowercase except where not using lowercase would cause a
nasty conflict between the portage tree and upstream (perl modules seem
to be the canonical example here).

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, Sparc, Mips)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] policy on case [in]sEnsiTiViTy to ebuild names

[Markus Nigbur]

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

On Thu, 2004-11-25 at 23:57 +0000, Ciaran McCreesh wrote:
> On Fri, 26 Nov 2004 00:49:25 +0100 Christian Parpart <trapni@gentoo.org>
> wrote:
> | I recently came into an issue of the ebuild names. usually I 
> | write them all lower case (that is: as-is), but recently, I 
> | run into packages to be submittet, that HavE different cAsEs. 
> | Namely the freedesktop's xlibs and xserver.
> <snip>
> | So, what's the policy on it?
> 
> In general, use lowercase except where not using lowercase would cause a
> nasty conflict between the portage tree and upstream (perl modules seem
> to be the canonical example here).

Isn't the unwritten policy to name the packages as they are named
upstream?
Admitted, if the developer(s) of a package think "MyP4cK4g3" would be
the best way to name their piece of software, it would looks quite
silly, but we don't need to confuse our users even more with naming our
package something more adequate, like "myp4ck4g3" or even "mypackage".

-- 
 (o_  Markus Nigbur
 //\  Gentoo Linux Developer
[ ]/_ http://www.gentoo.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] policy on case [in]sEnsiTiViTy to ebuild names

[Grant Goodyear]

[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]

Christian Parpart wrote: [Thu Nov 25 2004, 05:49:25PM CST]
> I recently came into an issue of the ebuild names. usually I 
> write them all lower case (that is: as-is), but recently, I 
> run into packages to be submittet, that HavE different cAsEs. 
> Namely the freedesktop's xlibs and xserver.
> 
> In xlibs, there're packages called libXcomposite, libX11 etc..
> I'd like to preserve the case in portage, too since doing 
> everything in lowercase doesn't really enheance readability 
> overall, and we already have (especially on dev-perl) packages
> that also have upper-cases anyway.
> 
> So, what's the policy on it?

As the developer handbook states: "[the package name] should contain
lowercase letters, the digits 0-9, and any number of single hyphen,
underscore, or plus characters. [...] We have some packages in Portage
that don't follow these rules, but _your_ packages should".

The long-standing policy is, indeed, that all package names should be
lowercase, and a bit of of bash trickery, MY_P=${P/FooBar/foobar}, makes
following this policy pretty straightforward.  Perl packages are an
(unwritten) exception to this rule mainly for historical reasons.

Hope that helps,
g2boojum
-- 
Grant Goodyear	
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0  9573 A6DC 7152 E0F6 5B76

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]