WHEREAS, Mandrake PPC always ends up using a few SRPMS that are similar but still different from the X86 version.
WHEREAS, Mandrake PPC Cooker, towards the end of the development cycle falls out of sync with Cooker x86. As a result the SRPMS for it start disappearing, unless they are identical to the released version. WHEREAS, In the process of making custom changes just for PPC that do not get rolled into x86 Mandrake may make patches to the source of various GPL programs. And the GPL requires that a "complete CORRESPONDING macine-readable source code" be distributed for any binary distribution (emphasis added by myself). And without the PPC specific SRPMS Mandrake would be in violation of the GPL. WHEREAS, It's a pain in the ass when you need the SRPM to a point release (e.g. 6.2mdk) on PPC but are unable to find the SRPM anywhere. THEREFOR, I propose that the following directory tree be made on the Mandrake mirrors: a) Mandrake-devel/cooker/SRPMS/ppc, would contain the SRPMS for cooker-ppc that differ from the current ones in X86, plus ones for packages that are point releases (as defined above). b) Mandrake/current/SRPMS/ppc, contains SRPMS for the current release of Mandrake PPC that differ from the SRPMS for the x86 version of the same release. This would minimize duplication on the mirrors but would make valuable SRPMS available. Additionally, I would propose a script be written that tracks whenever a x86 SRPM is being updated on the server and if ppc is still using it to move it to the appropriate SPRM folder before removing it. IOW to keep it in sync with the PPC. A similar script would watch the updates for RPMS of ppc and install the SRPM when given it for SRPMS where there has been some change made or for where the RPM has been updated to match the version in x86. In order for this to work it is critical that x86 and PPC versioning would precise for the RPMs. It would not be appropriate for PPC to release an RPM built from a different SRPM than the same version in x86. I believe this is already being adhered to. For the currently support versions of the distribution this would be extremly useful for security updates. As it stands now Stew and Vincent have to carefully hang on to these SRPMS so that if a security issue comes along they can fix PPC. This would eliminate this requirement and give the entire PPC community immediate and permanent access to Mandrakes's source changes. I hope this makes sense. -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org What difference does it make to the dead, the orphans, and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty and democracy? - Ghandi
