[gentoo-dev] Portage Ebuild Categories: a suggestion

[gentoo-dev] Portage Ebuild Categories: a suggestion

[Sean Mitchell]

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

Re: [gentoo-dev] Portage Ebuild Categories: a suggestion

[Maciek Borowka]

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

Re: [gentoo-dev] Portage Ebuild Categories: a suggestion

[Vitaly Kushneriuk]

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