On 14471 March 1977, Daniel Kahn Gillmor wrote: >> This could be done if someone sets up and runs an autobuilder for NEW. >> As this must be *strictly* limited, it won't integrate into the usual >> frameworks. > Can you describe what these strict limitations should be? That would > probably help anyone who comes along later interested in understanding > the scope of work involved.
- be in the US, so we dont export before they are cleared - strictly limited set of people who can access things. Right now thats FTPTeam (and by nature of unix rights, DSA) only. - A way to ensure we wont violate idiotic licenses - or a lawyer input that its not a problem in the limited scope of this autobuilder. That is, all of the usual stuff for main is no problem, but NEW contains non-free (and contrib) too - and people make mistakes. Put files with restrictions into NEW that would forbids building unless its for yourself (as an example) and we may have trouble. While currently we could point to the maintainer... Thats it just now, but its too early in the morning, i may have forgotten loads of things. :) >> Loads of work. None of us up to it for the forseable future. > that's too bad, but i guess people will just continue working around the > process by immediately re-uploading source-only packages after packages > make it through NEW :/ If that makes them happy... -- bye, Joerg
signature.asc
Description: PGP signature
