On Tue, Sep 14, 2010 at 12:14 AM, Steve Langasek firstname.lastname@example.org wrote:
On Mon, Sep 13, 2010 at 05:11:19PM -0400, James Westby wrote:
A further thought occurred to me the other day.
I assume that we have to put the source packages in the hwpack too, for at least the packages with some GPL code. Given that hwpacks also serve as a snapshot of the archive, we can't rely on a pointer to the original archive to serve the purpose.
Knowing which packages to include source for will be tricky, so I would implement this as source for all of them, at least to start with.
Is it intended that pre-release hwpacks will be long-lived? I expected the same rules to apply as to pre-release images: ephemeral objects used during development that would be replaced at release time by images built from the final archive, leaving no lingering obligation to provide easy access to source for images we're no longer distributing. Are the hwpacks not going to follow this same release cycle?
Right, I think legally we might really not be required to do this; however, technically it still makes sense to me to have the sources used to produce a certain hwpack. Especially since we use ppa's or some other archives for hwpacks which have no guarantees to keep history etc.