--- Johannes Winkelmann <jw@tks6.net> wrote:
First off all, I think we haven't managed to discuss all the items mentioned on the wiki page, but mainly because the hosting situation is not clear at all (on which many of the other tasks depend). Multiple efforts so resolve this are ongoing, or will start this week.
I should have a definite answer this week from UMass Dartmouth, as to whether or not they'll host us.
The new contrib collection is online, and as you've probably read public testing should start soon, certainly within this week.
HttpUp maintainers interested in participating, please email me your .httpup driver files from the email address you wish to receive clc-contrib@ notifications at. Also, be sure to tag your ports with .sync files.
The 'alias' discussion was not really extensive, but I guess we'll just introduce it and see how it feels, since it's completely restricted to prt-get at the moment. I plan to make a new release of prt-get later this week, or next weekend, incorporating the list of aliases.
Yay :) Can we review the list of aliases before this release?
Jukka has provided lists of ports with broken sources, and broken dependencies (deps which are not in contrib):
http://clc.morpheus.net:6999/clc/wiki?p=BrokenSources
http://clc.morpheus.net:6999/clc/wiki?p=MissingPorts I you haven't done so, please check those two lists.
I'll be adopting netpbm, and have indicated so on the MissingPorts list. If others would do so as well, we can avoid working to replace the same ports twice.
Till Biedermann has given us an update on his work on a new port database, which will be fully integrated in the wiki.
Sweet.
Finally, as a general impression, I liked the fact that it was a focused meeting and opportunity to discuss issues with multiple members of CLC. On the other hand, it was a bit long (three days) and we had too many items listed to discuss (well, we have many outstanding issues, but still).
I'd like to hear different opinions, but in general, I'd consider it a good idea to do something like this more regularly, say once per month, and maybe "just" two days.
Yea, that sounds reasonable. Even every-other-month would be an improvement, and is perhaps a bit more reasonable. Jay Dolan Software Engineer, Systems Analyst Windmill Cycles, Inc. 508.999.4000 __________________________________ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail