1 |
Is that true? |
2 |
|
3 |
my very scientific test of doing emerge -p ocaml on several machines |
4 |
returns that dev-lang/ocaml would be installed on every one. this would |
5 |
seem there is at least "some" mechanism defining which one is returned, |
6 |
even if its as silly as being alphebetical by by category name or ?? |
7 |
|
8 |
thanks for the link to the ebuild naming policy chris. it doesn't |
9 |
address this issue though of multiple ebuilds having the same name if |
10 |
they are in different categories. anyone have thoughts on how this |
11 |
should be done from a technical or user standpoint? i think from a user |
12 |
standpoint it makes more sense to allow multiple ebuilds with the same |
13 |
name because then a user searching for them will have both returned |
14 |
(even if they have to user the category/ebuild to get that particular |
15 |
one to install) |
16 |
|
17 |
dave |
18 |
|
19 |
On Tue, 2003-04-15 at 17:16, Jon Portnoy wrote: |
20 |
> They don't coexist happily. It's impossible to say definitively which |
21 |
> one you'll get when you emerge appname if appname exists in two |
22 |
> different categories. |
23 |
> |
24 |
> On Tue, Apr 15, 2003 at 05:42:43PM -0600, Dave Nellans wrote: |
25 |
> > do we have an established naming policy for ebuilds, and where can i |
26 |
> > find it? |
27 |
> > |
28 |
> > my gripe is that when i submitted the ebuild for a program named "balsa" |
29 |
> > (under app-sci/tbass) several devs told me i could not name it balsa |
30 |
> > because the gnome email client balsa already uses that name. i believed |
31 |
> > that is why apps were listed under app-sci, dev-db, etc... which is why |
32 |
> > this structure existed in the first place. i was told however this was |
33 |
> > not so and that this wasn't allowed. in the end the ebuild was called |
34 |
> > tbass which is very non-intuitive having a ebuild named something very |
35 |
> > dissimilar to its common name. |
36 |
> > |
37 |
> > all was fine untill i went to install ocaml and did emerge -s ocaml only |
38 |
> > to find there are TWO packages named ocaml that co-exist seemingly |
39 |
> > happily in different categories. this brings back my original question |
40 |
> > of if we have a specific naming policy or if some of the dev's are |
41 |
> > mistaken about things. |
42 |
> > |
43 |
> > if we don't have a naming policy yet, should we? it seems as if naming |
44 |
> > issues are becoming more significant now that the number of packages in |
45 |
> > portage continues to grow. |
46 |
> > |
47 |
> > any thoughts? |
48 |
> > dave |
49 |
-- |