From: David R. M. <dr...@fi...> - 2006-12-18 15:29:20
|
On Dec 18, 2006, at 7:12 AM, Dave Vasilevsky wrote: > > Now time for me to ask a question or two: What's the current > organization of the bindist mirrors? (Er...I'm assuming here that > it is actually mirrored.) How difficult would it be to make the > packages from the build farm available to devs or the general > public, via eg: rsync? We would need a way to clean up old debs > from any continuous build--fink cleanup can of course do this if > fink is installed on whatever machine is the source for the bindist > mirrors, but if not we'd have to write a custom script. Dave, We'd need a bit of additional infrastructure before making these available to the general public, in order to properly comply with the GPL. The issue is this: whenever we distribute a binary, we need to also make available the exact sources which were used to create that binary. My interpretation of this has been that we should supply not only the upstream source, as found in our distfiles mirror system, but also the fink info file and patch file. Moreover, we also need to keep the source files available for three years. So we would need a way of archiving info and source files, and being able to point someone to the precise info and source files which were used to create the binary. We do this already for the official bindists, by tagging the source and info files in CVS and storing a copy of the tagged files in the appropriate directory tree within the "Archive Browser" http://bindist.finkmirrors.net/bindist/dists/. We would need a system like that (an automated one, obviously) before making any public distribution. Notice that we are only actually *required* to do this for packages licensed under the GPL, but it has long been fink's policy to provide this high level of access for all non-restrictive packages. -- Dave |