![](https://secure.gravatar.com/avatar/a21a2b39bf7bcec3953d52a83d99ecd0.jpg?s=120&d=mm&r=g)
On 04/18/05 19:04 Till Biedermann 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.
yes, this is also true.
I suggest something like a checkbox "exclude httpups" in the search mask. Or favoring CLC-ports in the search result list.
Good idea, I suggest presenting the feature as an "also include external repositories" checkbox, maybe disabled by default.
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.
If including external repos gains general consensus, I think we'd then need a cron job that fills the sql database from both the local and remote sites. I say this not to go into iplementation details, but to highlight the fact that the sql source should be unique. While I don't think I'll personally have much use for external repos, it's ok for me to include them as well. The only negative aspect I'd like to highlight is that this could encourage "lazy" maintainers not to join the new contrib, with all the unpleasant consequences we have now (many dup ports, incompatibilities, etc.) -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com