From: Luke-Jr <luke-jr@gentoo.org>
To: George Shapovalov <george@gentoo.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] Breaking up the beast known as app-games
Date: Sat, 6 Sep 2003 13:38:19 +0000 [thread overview]
Message-ID: <200309061338.31818.luke-jr@gentoo.org> (raw)
In-Reply-To: <200309060047.32776.george@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ok, then maybe I should rephrase that... Ebuilds should not have the same
name. IIRC, it is against policy and when they do have the same name it is a
bug which should be fixed.
On Saturday 06 September 2003 07:47 am, George Shapovalov wrote:
> On Friday 05 September 2003 21:18, Luke-Jr wrote:
> > Obviously, ebuilds can't have the same name... For BitTorrent, the ebuild
>
> But they do. We already have few ebuilds with identical names in the tree
> (in different categories of course). I don't remember specifics, just that
> this was coming up in prior similar discussions and I think there are on an
> order of 10 of them.. Just pointing out "the fact of life" that we would
> have to be careful about when having to deal with actual reorganization.
> IIRC, some of them were emacs modules having the same name as the language
> or some such, for which they provided special emacs mode.
> And there were angry users when I had to rename ebuilds to avoid name
> clashes (f.e. balsa (the "oroginal" one, actually was created before the
> well known gnome app) => tbass). So this may not be as simple as it
> seems...
>
> George
>
>
>
> --
> gentoo-dev@gentoo.org mailing list
- --
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/WeNPZl/BHdU+lYMRAniaAKCZbsDxCTMJw2sNP4rkisy9dBcGjACghNsc
XvE6ts4smv9dnXYYTqrj/og=
=Kpkj
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-06 13:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 16:51 [gentoo-dev] Breaking up the beast known as app-games Mike Frysinger
2003-09-04 17:59 ` [gentoo-dev] Re: [gentoo-core] " Donny Davies
2003-09-04 18:07 ` Camille Huot
2003-09-04 19:02 ` Mike Frysinger
2003-09-04 19:45 ` Camille Huot
2003-09-04 20:14 ` Thomas de Grenier de Latour
2003-09-05 4:13 ` Mike Frysinger
2003-09-05 6:52 ` Thomas de Grenier de Latour
2003-09-05 8:15 ` Philippe Lafoucrière
2003-09-05 18:39 ` Thomas de Grenier de Latour
2003-09-06 0:17 ` Luke-Jr
2003-09-06 1:04 ` Mike Frysinger
2003-09-06 1:50 ` Thomas de Grenier de Latour
2003-09-06 2:03 ` Luke-Jr
2003-09-06 3:27 ` Robin H. Johnson
2003-09-06 4:18 ` Luke-Jr
2003-09-06 7:47 ` George Shapovalov
2003-09-06 13:38 ` Luke-Jr [this message]
2003-09-06 15:35 ` Martin Schlemmer
2003-09-07 0:06 ` Luke-Jr
2003-09-07 1:12 ` Martin Schlemmer
2003-09-06 8:48 ` Philippe Lafoucrière
2003-09-04 19:14 ` Luke-Jr
2003-09-04 19:42 ` Camille Huot
2003-09-04 19:45 ` Luke-Jr
2003-09-04 20:47 ` George Shapovalov
2003-09-04 20:52 ` Jean Jordaan
2003-09-04 22:09 ` Grant Goodyear
2003-09-04 22:26 ` Luke-Jr
2003-09-05 8:19 ` Jean Jordaan
2003-09-04 23:41 ` Daniel Robbins
2003-09-04 22:14 ` Jan Krueger
2003-09-05 8:22 ` [gentoo-dev] " Philippe Lafoucrière
2003-09-05 8:51 ` Ralph F. De Witt
2003-09-05 12:29 ` Mike Frysinger
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=200309061338.31818.luke-jr@gentoo.org \
--to=luke-jr@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=george@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