Hi, On Tue, Aug 29, 2006 at 15:22:18 +0200, Clemens Koller wrote:
Hello, Friends!
I see that my mail lead to some interesting discussion... [...] Johannes Winkelmann wrote:
How about fixing this issue once and for all and mirror all the core/opt distfiles somewhere central [...]
The main reason this isn't in place is the additional work needed to maintain those distfile mirrors.
I don't really see much additional work. I think it's sufficient to maintain one master and rsync n slaves. You have to trigger updates when a port is updated, and remove unnecessary files after a while (to avoid full HDDs; depending on the quality it's either really easy, or really hard to determine when to remove a file). Once this setup stands, it's probably little work keeping it up, however someone has to initially write and test these things.
I've done some preliminary testing for the triggering, however stopped due to lack of time and need. [...]
I (we) think to get a small root-server later in the project also for our above ppc product if it will get some package management, too. The server project is partly private, partly company related. But I see no problem to mirror a system/structure as long as there is free traffic. Sounds good; what does "as long as there is free traffic" mean here?
But what about an automated ports checker, who polls the dl servers every day once and sees if the port would build successfully? If no -> mail to the mailing list.... Good idea :-) Report from today: http://lists.crux.nu/pipermail/crux-devel/2006-August/001912.html
Summary URL http://crux.nu/files/check_urls.html According to that, the windowmaker problem is to be expected, the gtk isn't there... the tetex server for some reason rejects our requests, but works fine. Thanks for your interest, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch