1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Unless I'm mistaken, the only purpose of categories is to make it easier to |
5 |
find ebuilds either with tab completion or a GUI tree. |
6 |
|
7 |
On Saturday 06 September 2003 03:35 pm, Martin Schlemmer wrote: |
8 |
> On Sat, 2003-09-06 at 15:38, Luke-Jr wrote: |
9 |
> > -----BEGIN PGP SIGNED MESSAGE----- |
10 |
> > Hash: SHA1 |
11 |
> > |
12 |
> > Ok, then maybe I should rephrase that... Ebuilds should not have the same |
13 |
> > name. IIRC, it is against policy and when they do have the same name it |
14 |
> > is a bug which should be fixed. |
15 |
> |
16 |
> Having categories and having identical ones in different categories, |
17 |
> does sort of invalidate the extreme "bug" tag you put on it. Anyhow, |
18 |
> last time I checked, there was no policy like this ? As far as I am |
19 |
> concerned, as long as we have categories, renaming a package because |
20 |
> of an already existing one in a different category is just silly, and |
21 |
> will cause more confusion. |
22 |
> |
23 |
> > On Saturday 06 September 2003 07:47 am, George Shapovalov wrote: |
24 |
> > > On Friday 05 September 2003 21:18, Luke-Jr wrote: |
25 |
> > > > Obviously, ebuilds can't have the same name... For BitTorrent, the |
26 |
> > > > ebuild |
27 |
> > > |
28 |
> > > But they do. We already have few ebuilds with identical names in the |
29 |
> > > tree (in different categories of course). I don't remember specifics, |
30 |
> > > just that this was coming up in prior similar discussions and I think |
31 |
> > > there are on an order of 10 of them.. Just pointing out "the fact of |
32 |
> > > life" that we would have to be careful about when having to deal with |
33 |
> > > actual reorganization. IIRC, some of them were emacs modules having the |
34 |
> > > same name as the language or some such, for which they provided special |
35 |
> > > emacs mode. |
36 |
> > > And there were angry users when I had to rename ebuilds to avoid name |
37 |
> > > clashes (f.e. balsa (the "oroginal" one, actually was created before |
38 |
> > > the well known gnome app) => tbass). So this may not be as simple as it |
39 |
> > > seems... |
40 |
> > > |
41 |
> > > George |
42 |
> > > |
43 |
> > > |
44 |
> > > |
45 |
> > > -- |
46 |
> > > gentoo-dev@g.o mailing list |
47 |
> > |
48 |
> > - -- |
49 |
> > Luke-Jr |
50 |
> > Developer, Gentoo Linux |
51 |
> > http://www.gentoo.org/ |
52 |
> > -----BEGIN PGP SIGNATURE----- |
53 |
> > Version: GnuPG v1.2.3 (GNU/Linux) |
54 |
> > |
55 |
> > iD8DBQE/WeNPZl/BHdU+lYMRAniaAKCZbsDxCTMJw2sNP4rkisy9dBcGjACghNsc |
56 |
> > XvE6ts4smv9dnXYYTqrj/og= |
57 |
> > =Kpkj |
58 |
> > -----END PGP SIGNATURE----- |
59 |
> > |
60 |
> > |
61 |
> > -- |
62 |
> > gentoo-dev@g.o mailing list |
63 |
|
64 |
- -- |
65 |
Luke-Jr |
66 |
Developer, Gentoo Linux |
67 |
http://www.gentoo.org/ |
68 |
-----BEGIN PGP SIGNATURE----- |
69 |
Version: GnuPG v1.2.3 (GNU/Linux) |
70 |
|
71 |
iD8DBQE/WnZ4Zl/BHdU+lYMRAsIfAJ9n1q7mtvz1Wg3BoRNB3pVdizIR4QCfTS4H |
72 |
sHZl9oHKf07KCnwtCSJ7IOs= |
73 |
=bz3c |
74 |
-----END PGP SIGNATURE----- |
75 |
|
76 |
|
77 |
-- |
78 |
gentoo-dev@g.o mailing list |