From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild naming policy
Date: Tue, 15 Apr 2003 17:11:23 -0700 [thread overview]
Message-ID: <200304151711.23346.george@gentoo.org> (raw)
In-Reply-To: <1050451387.18805.17.camel@malfus>
Hey Dave.
I feel your pain ;), I was the one responsible for the package, so I think I
need to do some discussion/explanation here.
While I myself sympathise to the more structured approach and would wellcome
distinguishing packages by categories, the sad truth is that portage does not
seem to be very consistent even with itself, as Fred Van Andel pointed out.
Now, not so sad truth :)
I just wanted to point out, that originallly portage was category-sensitive,
and you *had* to specify categiry while emerging the package. The change was
made quite consciousnessly, as this feature (of being able to drop category)
was quite requested one (if memory serves me well). Heck, I even catch myself
now and then enjoing not to have to type too much :).
Of course the change has implications, that certain category treatment is not
followed, which can lead to the problems, some of which (albeit minor at this
point) were emphasized.
As for the existance of two ocaml's: the thing is that this did not become a
strict policy, while it probably should have, and the developer in question
might not have known about it.
Thus I would like to use your request as a bait for other developers and users
to discuss the issue and decide whether we should "officialize" this policy
(of not having equivalently named ebuilds under different categories) or
should we do something else. However IMHO leaving this as "unofficial" policy
may hart in the long run...
George
On Tuesday 15 April 2003 17:03, Dave Nellans wrote:
> Is that true?
>
> my very scientific test of doing emerge -p ocaml on several machines
> returns that dev-lang/ocaml would be installed on every one. this would
> seem there is at least "some" mechanism defining which one is returned,
> even if its as silly as being alphebetical by by category name or ??
>
> thanks for the link to the ebuild naming policy chris. it doesn't
> address this issue though of multiple ebuilds having the same name if
> they are in different categories. anyone have thoughts on how this
> should be done from a technical or user standpoint? i think from a user
> standpoint it makes more sense to allow multiple ebuilds with the same
> name because then a user searching for them will have both returned
> (even if they have to user the category/ebuild to get that particular
> one to install)
>
> dave
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-16 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 23:42 [gentoo-dev] ebuild naming policy Dave Nellans
2003-04-15 23:16 ` Jon Portnoy
2003-04-16 0:03 ` Dave Nellans
2003-04-15 23:43 ` Fred Van Andel
2003-04-16 0:11 ` George Shapovalov [this message]
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=200304151711.23346.george@gentoo.org \
--to=george@gentoo.org \
--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