Thomas Sailer schreef op do 05-05-2011 om 17:59 [+0200]:
Hi Erik,
the new mingw guidelines seem to create a bit of a migration issue; since the source package name changes, there probably needs to be new repositories created for all mingw32 packages for f16+
Is there going to be a mass migration of some sort? or do we need to re-review all packages?
And how am I going to request a new package repository with different names for <=f15 and >=f16?
The problem right now is that the new guidelines seem to confuse Jason Tibbitts to the point where he refuses SCM requests...
Tom
Hi Thomas,
I just replied to the review ticket about the current situation.
With regard to your question about migration: there isn't any clear plan yet to mass-rename all mingw32-* packages. According to the regular proces we've got to file rename requests for all mingw32-* packages and have them re-reviewed. But as we're close to 100 different mingw32-* packages this isn't really a feasible method. Perhaps we can ask FeSCO to give us an exception so we can mass-rename all mingw32-* packages without having to get everything through the review proces again.
Kind regards,
Erik van Pienbroek
On Thu, 2011-05-05 at 18:39 +0200, Erik van Pienbroek wrote:
packages this isn't really a feasible method. Perhaps we can ask FeSCO to give us an exception so we can mass-rename all mingw32-* packages without having to get everything through the review proces again.
+1