From: Vitaly Kushneriuk <vitaly_kushneriuk@yahoo.com>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Portage Ebuild Categories: a suggestion
Date: 07 Feb 2002 17:47:32 +0200 [thread overview]
Message-ID: <1013096852.10720.4.camel@uranus.u235.eyep.net> (raw)
In-Reply-To: <3C629988.CF7D7AFA@ifaedi.insa-lyon.fr>
Read the previous thread at the subject...
I proposed a KEYWORDS="..." variable in the ebuild.
Then you can grep the tree, or even better, after rsync, you can run
something like "emerge --update-keywords" to create number of files,
one for every found keyword, with names of ebuilds that contain it.
The problem is that we are failrly close to v. 1.0 and fixing
existing bugs is a higher priority then adding new features. My bet is
we _will_ implement something to solve the problem, but it most probably
will be after Gentoo 1.0 release.
/Vitaly.
On Thu, 2002-02-07 at 17:13, Maciek Borowka wrote:
> Hmm...
>
> I like it.
>
> If we do that; we could put a nice script to list all the packages from one
> category,
> so perhaps something like :
>
> DESCRIPTION="A graphical file comparator and merge tool simular to xdiff."
> EMERGE_CATEGORY="dev-util"
> EMERGE_CATEGORY="x11-misc"
> SRC_URI="http://prdownloads.sourceforge.net/xxdiff/${P}.src.tar.gz"
>
>
> would be better (simple grep would then do what we want)...
>
> /Maciek
>
>
> Sean Mitchell wrote:
>
> > 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
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
prev parent reply other threads:[~2002-02-07 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 15:02 [gentoo-dev] Portage Ebuild Categories: a suggestion Sean Mitchell
2002-02-07 15:13 ` Maciek Borowka
2002-02-07 15:47 ` Vitaly Kushneriuk [this message]
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=1013096852.10720.4.camel@uranus.u235.eyep.net \
--to=vitaly_kushneriuk@yahoo.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