On Tue, Feb 3, 2009 at 6:47 AM, Mart Raudsepp <l...@gentoo.org> wrote:
> I agree that a tag kind of approach would be nice. Someone should
> actually do work on it.
> Here's a random similar idea that I think might work well as a GLEP
> proposition, that I was about to reply to a different subthread before
> noticing this post:
<snip random idea :p>
The simplest method I can think of is:
${PORTDIR}/tags/games/puzzles/ksudoku -> ../../../kde-base/ksudoku
Yes, that's a symlink inside a new root-directory "tags" where "games"
is a tag and "puzzles" is a sub-tag. If for some reason we get an
explosion in sudoku games in portage (with weird names), we can make a
new sub-tag "games/puzzles/sudoku/"
${PORTDIR}/tags/games/puzzles/sudoku/ksudoku -> ../../../../kde-base/ksudoku
And this won't cause any problems since "higher" tags are inherited.
Another usage of tagging could be marking packages as "deprecated" to
ease out removal of old packages.
${PORTDIR}/tags/dying/amarok -> ../media-sound/amarok
/me hides from the amarok lovers.
Symlinking has the advantage of being a natural extension of our
favourite flat-file db[1] to tagging. Having a new folder instead of
symlinking inside other categories has the advantage of being
backwards-compatible, and will also prevent an explosion in the number
of categories in the root dir.
FWIW, git (atleast) preserves symlinks in source trees, so once the
move to git is complete, there will be no obstacles left in this
thing's implementation ;)
1. That's the portage tree, btw :p
--
~Nirbheek Chauhan
