From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] policy on case [in]sEnsiTiViTy to ebuild names
Date: Fri, 26 Nov 2004 12:49:04 -0600 [thread overview]
Message-ID: <20041126184904.GA9438@server.grantgoodyear.org> (raw)
In-Reply-To: <200411260049.27765.trapni@gentoo.org>
[-- 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 --]
prev parent reply other threads:[~2004-11-26 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 23:49 [gentoo-dev] policy on case [in]sEnsiTiViTy to ebuild names Christian Parpart
2004-11-25 23:57 ` Ciaran McCreesh
2004-11-26 11:59 ` Markus Nigbur
2004-11-26 18:49 ` Grant Goodyear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041126184904.GA9438@server.grantgoodyear.org \
--to=g2boojum@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox