| 1 |
On Thu, 2004-11-25 at 23:57 +0000, Ciaran McCreesh wrote: |
| 2 |
> On Fri, 26 Nov 2004 00:49:25 +0100 Christian Parpart <trapni@g.o> |
| 3 |
> wrote: |
| 4 |
> | I recently came into an issue of the ebuild names. usually I |
| 5 |
> | write them all lower case (that is: as-is), but recently, I |
| 6 |
> | run into packages to be submittet, that HavE different cAsEs. |
| 7 |
> | Namely the freedesktop's xlibs and xserver. |
| 8 |
> <snip> |
| 9 |
> | So, what's the policy on it? |
| 10 |
> |
| 11 |
> In general, use lowercase except where not using lowercase would cause a |
| 12 |
> nasty conflict between the portage tree and upstream (perl modules seem |
| 13 |
> to be the canonical example here). |
| 14 |
|
| 15 |
Isn't the unwritten policy to name the packages as they are named |
| 16 |
upstream? |
| 17 |
Admitted, if the developer(s) of a package think "MyP4cK4g3" would be |
| 18 |
the best way to name their piece of software, it would looks quite |
| 19 |
silly, but we don't need to confuse our users even more with naming our |
| 20 |
package something more adequate, like "myp4ck4g3" or even "mypackage". |
| 21 |
|
| 22 |
-- |
| 23 |
(o_ Markus Nigbur |
| 24 |
//\ Gentoo Linux Developer |
| 25 |
[ ]/_ http://www.gentoo.org |
Archives