--- Till Biedermann <tillbiedermann@yahoo.de> wrote:
The advantage of including all httpups in the database is that you have one point where you can search for ports in the whole CRUX-universe.
I suggest something like a checkbox "exclude httpups" in the search mask. Or favoring CLC-ports in the search result list.
I agree with the idea that the portdb on the CRUX/CLC website should only list CRUX/CLC ports. But from the point of view of an average user it is annoying to have two databases or actually none for httpups.
Hi all. I'm sorry I've been relatively quiet throughout this discussion. Sip, I *really* like what you've done so far. It's excellent. In regards to the forum, my opinion is rather neutral. It would not bother me if we had one, unless it detracted from the ML and/or caused confusion/redundancy. With respect to subprojects, I would like to see all of our one-off tools bear a project page on the portal. Imo, this includes things like prt-get, yapo, prt-utils, pkgsync, et al. If we are going to promote subproject development, it only makes sense to put our current subprojects into this same place. It would present a more unified vision to users. As far as [a rewritten] portdb is concerned, I think this would be a good time to talk about creating a common c library for manipulating ports and packages. We spoke briefly about this at CC2K4, but I don't know if any progress has been made since. Pkgutils, prt-get, and others could greatly benefit from such a library. It would also allow other projects, like a new portdb, to be developed rapidly. I would be interested in contributing to an effort to produce this. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail