public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markus Nigbur <pyrania@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:59:31 +0100	[thread overview]
Message-ID: <1101470371.13153.4.camel@powerix> (raw)
In-Reply-To: <20041125235759.40cc14ba@snowdrop.home>

[-- 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 --]

  reply	other threads:[~2004-11-26 12:00 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 [this message]
2004-11-26 18:49 ` Grant Goodyear

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=1101470371.13153.4.camel@powerix \
    --to=pyrania@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