From: Sean Mitchell <SMitchell@phoenix-interactive.com>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Portage Ebuild Categories: a suggestion
Date: Thu, 7 Feb 2002 10:02:41 -0500 [thread overview]
Message-ID: <23DFAA462CC6A64487613B0E242D9FF706EB76@mercury.phoenix-interactive.com> (raw)
This is probably the single biggest issue on this list. It seems that every
day there's a post questioning why an ebuild is in a given location and not
some other.
I really don't see how anyone could ever come up with a structure that's
intuitive for everyone... we just don't all think the same way. For myself,
I don't even bother with the structure, I prefer to do a find on *.ebuild in
/usr/portage to see what's there.
A few years ago I put together a series of OS/2 shareware CDs and had the
same problem - many packages didn't clearly fit in one place or another.
The solution I came up with and the one I suggest here is that the
categories be eliminated altogether. in this case one big /usr/portage with
a directory for each package.
I mean, it's easy enough to grep the description fields, or even put all
possible categories in a new tag in the ebuild. It would be simple to put
together some tools to show the packages by category if desired.
Something like:
S=${WORKDIR}/${P}
DESCRIPTION="A graphical file comparator and merge tool simular to xdiff."
CATEGORY="dev-util x11-misc"
SRC_URI="http://prdownloads.sourceforge.net/xxdiff/${P}.src.tar.gz"
HOMEPAGE="http://xxdiff.sourceforge.net/"
What do you think?
Sean
next reply other threads:[~2002-02-07 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 15:02 Sean Mitchell [this message]
2002-02-07 15:13 ` [gentoo-dev] Portage Ebuild Categories: a suggestion Maciek Borowka
2002-02-07 15:47 ` Vitaly Kushneriuk
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=23DFAA462CC6A64487613B0E242D9FF706EB76@mercury.phoenix-interactive.com \
--to=smitchell@phoenix-interactive.com \
--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