The correct maner to obsolete subpackage.

The correct maner to obsolete subpackage.

[Takashi Yano]

If the main package no longer provides a sub package,
what is the correct maner to bosolete it?

Creating empty sub package with
sub_package_CATEGORY="_obsolete"
is correct?

Or just deleting the sub pcakege?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

Re: The correct manner to obsolete subpackage.

[Jon Turney]

On 29/08/2023 23:40, Takashi Yano via Cygwin-apps wrote:
> If the main package no longer provides a sub package,
> what is the correct manner to osolete it?
> 
> Creating empty sub package with
> sub_package_CATEGORY="_obsolete"
> is correct?

To answer the question correctly, I need to know what you want to happen 
for people who have the subpackage installed currently.

If the package is replaced or superseded by a different package (so 
sub_package should get uninstalled, and replacement_package installed 
instead), just write:

replacement_package_OBSOLETES="sub_package"

If the package is really being removed without any replacement, there 
are mechanisms to deal with that case, but that case should be really rare.

> Or just deleting the sub package?

Generally, you never want to do this, at it means the current version 
will linger, remaining installed (potentially with (currently 
unreported) file conflicts with any replacement).

Re: The correct manner to obsolete subpackage.

[Takashi Yano]

Hi Jon,

Thanks the answer.

On Wed, 30 Aug 2023 13:43:15 +0100
Jon Turney wrote:
> On 29/08/2023 23:40, Takashi Yano via Cygwin-apps wrote:
> > If the main package no longer provides a sub package,
> > what is the correct manner to osolete it?
> > 
> > Creating empty sub package with
> > sub_package_CATEGORY="_obsolete"
> > is correct?
> 
> To answer the question correctly, I need to know what you want to happen 
> for people who have the subpackage installed currently.
> 
> If the package is replaced or superseded by a different package (so 
> sub_package should get uninstalled, and replacement_package installed 
> instead), just write:
> 
> replacement_package_OBSOLETES="sub_package"

Yeah, I found this in some packages.

But, my case is

> If the package is really being removed without any replacement, there 
> are mechanisms to deal with that case, but that case should be really rare.

this. pulseaudio package no longer provides esound and gconf,
however, these packages are exist in current pulseaudio package.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-a10d836640

The these old package is not compatible with new pulseaudio, so
these should be going to uninstall.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

Re: The correct manner to obsolete subpackage.

[ASSI]

Takashi Yano via Cygwin-apps writes:
> But, my case is
>
>> If the package is really being removed without any replacement, there 
>> are mechanisms to deal with that case, but that case should be really rare.
>
> this. pulseaudio package no longer provides esound and gconf,
> however, these packages are exist in current pulseaudio package.
> https://bodhi.fedoraproject.org/updates/FEDORA-2021-a10d836640
>
> The these old package is not compatible with new pulseaudio, so
> these should be going to uninstall.

The correct solution would be declare whatever provides suitable
functionality as a replacement package, even if it doesn't provide the
exact same commands, IMHO.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Re: The correct manner to obsolete subpackage.

[Brian Inglis]

On 2023-08-29 16:40, Takashi Yano via Cygwin-apps wrote:
> If the main package no longer provides a sub package,
> what is the correct manner to obsolete it?

OBSOLETES=sub_pkg

or

pkg_OBSOLETES="sub_pkg1 sub_pkg2 ..."

> Creating empty sub package with
> sub_package_CATEGORY="_obsolete"
> is correct?

That's more appropriate for a rename/replace e.g.

old_pkg_CATEGORY=_obsolete
old_pkg_SUMMARY="obsolete name for libpkg-devel"
old_pkg_CONTENTS= # empty
old_pkg_REQUIRES=libpkg-devel

> Or just deleting the sub package?

How would you do that?
Not producing it leaves the old release around.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

Re: The correct manner to obsolete subpackage.

[Takashi Yano]

On Wed, 30 Aug 2023 10:59:30 -0600
Brian Inglis wrote:
> On 2023-08-29 16:40, Takashi Yano via Cygwin-apps wrote:
> > If the main package no longer provides a sub package,
> > what is the correct manner to obsolete it?
> 
> OBSOLETES=sub_pkg
> 
> or
> 
> pkg_OBSOLETES="sub_pkg1 sub_pkg2 ..."

This seems to work for me as expected.
Thanks!

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>