From: Dave Nellans <dnellans@cs.utah.edu>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] ebuild naming policy
Date: 15 Apr 2003 17:42:43 -0600 [thread overview]
Message-ID: <1050450162.18807.6.camel@malfus> (raw)
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
do we have an established naming policy for ebuilds, and where can i
find it?
my gripe is that when i submitted the ebuild for a program named "balsa"
(under app-sci/tbass) several devs told me i could not name it balsa
because the gnome email client balsa already uses that name. i believed
that is why apps were listed under app-sci, dev-db, etc... which is why
this structure existed in the first place. i was told however this was
not so and that this wasn't allowed. in the end the ebuild was called
tbass which is very non-intuitive having a ebuild named something very
dissimilar to its common name.
all was fine untill i went to install ocaml and did emerge -s ocaml only
to find there are TWO packages named ocaml that co-exist seemingly
happily in different categories. this brings back my original question
of if we have a specific naming policy or if some of the dev's are
mistaken about things.
if we don't have a naming policy yet, should we? it seems as if naming
issues are becoming more significant now that the number of packages in
portage continues to grow.
any thoughts?
dave
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-04-15 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 23:42 Dave Nellans [this message]
2003-04-15 23:16 ` [gentoo-dev] ebuild naming policy Jon Portnoy
2003-04-16 0:03 ` Dave Nellans
2003-04-15 23:43 ` Fred Van Andel
2003-04-16 0:11 ` George Shapovalov
2003-04-16 0:58 ` Dave Nellans
2003-04-16 0:35 ` Peter Ruskin
2003-04-16 1:39 ` Jeff Rose
2003-04-16 2:43 ` George Shapovalov
2003-04-16 8:15 ` Paul de Vrieze
2003-04-16 13:30 ` Chris Bainbridge
2003-04-15 23:20 ` Chris PeBenito
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=1050450162.18807.6.camel@malfus \
--to=dnellans@cs.utah.edu \
--cc=gentoo-dev@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