On Sun, May 12, 2013 at 01:29:05PM +0100, Gerard Ryan wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/12/2013 11:20 AM, Björn Esser wrote:
> Hello Gerard!
>
> EOL procedure on the wiki explicitly names this as first step: Make
> sure the package is properly Obsoleted/Provided by something if it
> is being replaced, see Renaming/Replacing Guidelines (on wiki).
>
> Since you have pkgfoo-split1 and pkgfoo-split2 and you probably
> want to merge them into pkgfoo, i'd suggest to have
> Obsolete/Provides like this inside the merged pkg:
>
> Obsoletes: pkgfoo-split1 <= $LAST_VER_IN_F18 Obsoletes:
> pkgfoo-split2 <= $LAST_VER_IN_F18 Provides: pkgfoo-split1 =
> %{version} Provides: pkgfoo-split2 = %{version}
>
> If you have pkgfoo and pkgfoo-split and you probably want to merge
> them into pkgfoo, i'd suggest to have Obsolete/Provides like this
> inside the merged pkg:
>
> Obsoletes: pkgfoo <= $LAST_VER_IN_F18 Obsoletes: pkgfoo-split <=
> $LAST_VER_IN_F18 Provides: pkgfoo-split = %{version}
>
> Just my two cents.
>
> BR, Björn
>
> Am Sonntag, den 12.05.2013, 04:08 -0500 schrieb Jon Ciesla:
>> Sorry for top post, mobile. I think given the lack of builds toy
>> can skip Obsoletes and Provides, and can just follow the EOL
>> procedure on the wiki.
>>
>> On May 11, 2013 6:01 PM, "Gerard Ryan"
>> <galileo(a)fedoraproject.org> wrote:
> <snip>
Thanks for the replies guys. It's the second scenario in what you've
mentioned Björn, there's pkgfoo and pkgfoo-split. The reason I was
asking was because I was thinking along the lines of what Jon says --
that maybe obsoletes/provides can be skipped. I guess since it's my
first time EOL'ing a package, there's no harm in me explicitly putting
them in, just to make sure.
If the package pkgfoo-split has never been built then you and Jon are right
that Obsolets/Provides are unneeded. However, as you say, there's no harm
in having it in there.
-Toshio