On 06/27/2011 07:23 AM, Jesús J. Guerrero Botella wrote: > I still don't understand why > > A) you need to build a project, a glep, whatever the course of action > is, I am bad at bureaucracy. > B) you need to code the solution, to fix What?
Some people requested a "tags" feature. I'm not sure if "fix" is the best word. Tags will provide a new way to search for packages, that's all. > C) "ls $PORTDIR/whatever-category" is a command that's way simpler > than the one you posted. There are lots of possible approaches. See Ciaran's "Are tags just sets?" approach that is very similar to your suggested symlink approach, except that it represents a tag using a text file containing a list of packages instead of a directory containing symlinks. > XML seems to be the trend, but we should really think a moment, what's > what we are trying to fix? Again, maybe "fix" isn't the best word. I believe that the goal it to provide a new method of searching that is based on tags. > We just needed to add some categories or rename them when someone > started this thread, but now, even when we know we are lacking dev > power in some areas we start arguing that the base concept of our OS > (portage) is wrong, and that we should redo it completely by putting > every ebuild into a directory and tagging them. I would advise against going down the "redo it completely" path, since it's relatively easy to implement a tagging mechanism that will coexist with the existing category framework. > Again, that's not "port-age". Read on ports: > > http://en.wikipedia.org/wiki/FreeBSD_Ports Interestingly, the wiki page that you linked has a link to a project to add tags to the ports collection: http://www.tobez.org/port-tags/ > I don't even use tags for my music collections and now I am going to > be forced to use them to operate my OS. Again, I would advise against going down the "redo it completely" path that this statement implies, given that it's relatively easy to implement a tagging mechanism that will coexist with the existing category framework. -- Thanks, Zac
