Looks like it's back online now so no need for any immediate action. We also have an obligation to provide source code for everything we ship as part of each LEAF distribution, in order to comply with the terms of most of the open source licenses, and it's *much* easier to do that if we have a copy of the source in our own repository. There isn't quite such a strict requirement for the buildenv / toolchain since that is not (currently) made available in compiled form.
Personally I don't have a problem with us maintaining copies of upstream source code in our own repository. It's not a huge volume of data and we've had problems with even "reliable" repositories like kernel.org being taken offline in the past. IMHO it's better to isolate from such issues. The maintenance overhead is not too bad. david On 2 Jun 2012, at 16:16, Andrew wrote: > In any case, keeping everything up-to-date means manual update of > package files. Earlier we have sources from 'stable' foreign servers out > of tree, but when kernel.org goes down we choose to have all sources in > the tree. > > 02.06.2012 18:09, Erich Titl ???????: >> on 02.06.2012 14:45, Andrew wrote: >>> In any case, most of the packages are already in repo. >> True, but questionable >> >> In case of >>> foreign repo - we need to change paths every time when package is moved >>> on the server into other place, and in case of server failure/package >>> deletion we'll have a headache. >> I guess this is the fate of any system integrator. We have headaches >> also by the need to keep everything up to date :-) >> >> I just hate redundancy >> >> cheers >> >> Erich ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
