Andi Payn <[EMAIL PROTECTED]> writes: > A quick urpmf --media main-cooker,contrib-cooker --provides "" |grep > gimp-data-min shows nothing relying on this; is that a good enough > test to be sure it's safe, or do we also have to make sure that > non-Mandrake-provided packages (plf, nexedi, whatever) don't need > it?
these're there to help updating from older releases. i guess we can remove the provides from gimp1_3 and keept the "obsoletes ... < X.Y.Z" in both gimps. > [about hackgimp being provided and obsoleted by both] > > | we cannot change the past, only the future, so here's the > > | hackgimp definition. > > > > This is true, for gimp 1.2. But for 1.3, I guess we don't need to > > provide/obsolete hackgimp again. of course we do since we expect gimp1_3 to became the new stable gimp one day ... > Again, is it ok to remove hackgimp now when it was already in the > 9.1 release of gimp1_3? (The same test as above shows nothing in > Cooker requires hackgimp either.) we cannot change the past so we want to keep the needed stuff to update from older releases
