--- Till Biedermann wrote:
Hi,
most of you might have noticed that I made a frontend to the mysql-based portsdatabase on crux.nu availible in the wiki:
Lookin good :) I take it you plan to implement viewing the port (Pkgfile, .footprint, etc..) soon?
1.) How should the application procedure for the portdb look like?
The simple solution is we allow only repos which take part in the new contrib. So the quality of ports and active maintenance guaranteed.
The other way is that every repo can be listed in the db. In this case should there be a registration form (like it is now with the old db) or is it better to use the mailing list (like we do for everything)?
I don't have strong feelings either way. I think, perhaps, that showing ports from all repositories might be nice.
2.) The other question is how to handle .sync-tagged (i.e. contrib-) ports in the origin repository? The old db lists the port both in contrib and in the httpup repo (which falsifies the duplicate stats btw.). I think it is better to exclude contrib ports from the origin httpup repo in the db listing. What do you think?
Yea, I like that - each port only shows up once. *Or* you could show them in the original httpup, too, perhaps with some visual cue, indicating that it's also available in contrib. :) Nice job, thanks for working on this. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com