From: Martin Schlemmer <azarah@gentoo.org>
To: Luke-Jr <luke-jr@gentoo.org>
Cc: George Shapovalov <george@gentoo.org>,
Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-core] Breaking up the beast known as app-games
Date: Sun, 07 Sep 2003 03:12:00 +0200 [thread overview]
Message-ID: <1062897120.8455.43.camel@nosferatu.lan> (raw)
In-Reply-To: <200309070006.21510.luke-jr@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 5460 bytes --]
On Sun, 2003-09-07 at 02:06, Luke-Jr wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Unless I'm mistaken, the only purpose of categories is to make it easier to
> find ebuilds either with tab completion or a GUI tree.
>
Well, the other idea is to have things a bit more structured. Sure,
some things belong to more categories than one, but most if not all
of the times it is more suited in one, so we can have it there.
I never was fond of the 'flat' structure, as it in my opinion will
make things more difficult. Where you can now just do:
$ ls /usr/portage/x11-themes/
to see what themes X there is, you will either have to search for
'theme' and hope you do not get buried under the load, or you will
have to first dig through another file for the 'virtual category',
and then search for that. It will also be slower then the 'ls'
alternative.
Further, maintaining will also get a bigger headache, as you will
have to keep updated as 'virtual categories' are added and changed,
and maintain the not so short to too damn long list for each
package.
But all above have still nothing to do with:
1) I see no issue with 'foo/bar' and 'zar/bar' packages, as portage
will get the DEPEND right, and it is really not that a train smash for
the user.
2) I still am fairly sure there is no policy that say you cannot
have 1), as you wanted to relay.
3) Except if changed, the policy 'was' that all package names should
be lower case ... guess nobody bother about that one 8)
Lastly, I really do not see the gain in dumping all packages starting
with 'a' into a[0-9]. I have never been a Slackware fan (local history
that I am not going to go into now), but every time I wanted to browse
their packages (or Suse for that matter), its a rather mission to
figure out where what is, especially if you do not know the exact name
of the package. MDK/RH is a bit better, but the 20 pages with a 'ls'
also tend to make it a schlep - Gentoo has been fairly easy to find
most things when I started (did not have the 'emerge -s ...' back then.
Right, so maybe its because I came from before 'emerge -s', or maybe it
is because I mostly still navigate with 'cd' and 'ls'. I do however
feel that just dumping the categories as we have them now will be a
more in the wrong direction. Sure, you have editors, and then you have
a editor for java - where to put it? If not a plain text editor, but
rather something like rhide, anjuta, whatever, they are in dev-util.
Sure not the best place .. what about a new category 'dev-ide' ?
There is a few IDE's around these days.
Anyhow, just me rambling, flame away =)
> On Saturday 06 September 2003 03:35 pm, Martin Schlemmer wrote:
> > On Sat, 2003-09-06 at 15:38, Luke-Jr wrote:
> > > -----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.
> >
> > Having categories and having identical ones in different categories,
> > does sort of invalidate the extreme "bug" tag you put on it. Anyhow,
> > last time I checked, there was no policy like this ? As far as I am
> > concerned, as long as we have categories, renaming a package because
> > of an already existing one in a different category is just silly, and
> > will cause more confusion.
> >
> > > 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
>
> - --
> Luke-Jr
> Developer, Gentoo Linux
> http://www.gentoo.org/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQE/WnZ4Zl/BHdU+lYMRAsIfAJ9n1q7mtvz1Wg3BoRNB3pVdizIR4QCfTS4H
> sHZl9oHKf07KCnwtCSJ7IOs=
> =bz3c
> -----END PGP SIGNATURE-----
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-07 1:08 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
2003-09-06 15:35 ` Martin Schlemmer
2003-09-07 0:06 ` Luke-Jr
2003-09-07 1:12 ` Martin Schlemmer [this message]
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=1062897120.8455.43.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=george@gentoo.org \
--cc=luke-jr@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