Process for retiring a subpackage

Process for retiring a subpackage

[Adam Dinwoodie]

Per previous discussion on this list, I'm planning on retiring the
separate packaging of Bash completion scripts in the packages I
maintain, and folding the files into the main package.  I can't find any
documentation that'll hold my hand through that process, so can somebody
with the relevant arcane knowledege check my understanding of what's
necessary?

Taking git-completion as an example, where I'm moving all the contents
from that package into the main git package:

- For the first release that obsoletes git-completion:

  - Create the main git package in such a way that it contains the files
    that would previously have been in git-completion.

  - Create a dummy git-completion package that:

    - Has a dependency on the git package (which it normally does
      anyway).
    - Has a category of "_obsolete".
    - Has no actual content.

  - Create the rest of the release as normal.

- For following releases:

  - Continue to create all the packages as normal (excluding
    git-completion).

  - Don't bother to create new versions of the git-completion package.

The above process is cobbled together from memory of emails going past
this list, so I'd appreciate someone checking I've understood correctly.

Re: Process for retiring a subpackage

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]

On Mar 17 12:04, Adam Dinwoodie wrote:
> Per previous discussion on this list, I'm planning on retiring the
> separate packaging of Bash completion scripts in the packages I
> maintain, and folding the files into the main package.  I can't find any
> documentation that'll hold my hand through that process, so can somebody
> with the relevant arcane knowledege check my understanding of what's
> necessary?
> 
> Taking git-completion as an example, where I'm moving all the contents
> from that package into the main git package:
> 
> - For the first release that obsoletes git-completion:
> 
>   - Create the main git package in such a way that it contains the files
>     that would previously have been in git-completion.
> 
>   - Create a dummy git-completion package that:
> 
>     - Has a dependency on the git package (which it normally does
>       anyway).
>     - Has a category of "_obsolete".
>     - Has no actual content.
> 
>   - Create the rest of the release as normal.
> 
> - For following releases:
> 
>   - Continue to create all the packages as normal (excluding
>     git-completion).
> 
>   - Don't bother to create new versions of the git-completion package.
> 
> The above process is cobbled together from memory of emails going past
> this list, so I'd appreciate someone checking I've understood correctly.

Sounds completely right to me.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: Process for retiring a subpackage

[Yaakov Selkowitz]

On 2016-03-17 07:04, Adam Dinwoodie wrote:
> Per previous discussion on this list, I'm planning on retiring the
> separate packaging of Bash completion scripts in the packages I
> maintain, and folding the files into the main package.  I can't find any
> documentation that'll hold my hand through that process, so can somebody
> with the relevant arcane knowledege check my understanding of what's
> necessary?
>
> Taking git-completion as an example, where I'm moving all the contents
> from that package into the main git package:
>
> - For the first release that obsoletes git-completion:
>
>    - Create the main git package in such a way that it contains the files
>      that would previously have been in git-completion.
>
>    - Create a dummy git-completion package that:

Simpler:

git_OBSOLETES="git-completion"

Just leave this in indefinitely.

-- 
Yaakov

Re: Process for retiring a subpackage

[Jon Turney]

On 17/03/2016 15:46, Yaakov Selkowitz wrote:
> On 2016-03-17 07:04, Adam Dinwoodie wrote:
>> Per previous discussion on this list, I'm planning on retiring the
>> separate packaging of Bash completion scripts in the packages I
>> maintain, and folding the files into the main package.  I can't find any
>> documentation that'll hold my hand through that process, so can somebody
>> with the relevant arcane knowledege check my understanding of what's
>> necessary?
>>
>> Taking git-completion as an example, where I'm moving all the contents
>> from that package into the main git package:
>>
>> - For the first release that obsoletes git-completion:
>>
>>    - Create the main git package in such a way that it contains the files
>>      that would previously have been in git-completion.
>>
>>    - Create a dummy git-completion package that:
>
> Simpler:
>
> git_OBSOLETES="git-completion"
>
> Just leave this in indefinitely.

This is probably better, because:

>> - For following releases:
>>
>>    - Continue to create all the packages as normal (excluding
>>      git-completion).
>>
>>    - Don't bother to create new versions of the git-completion package.

There is a slight additional wrinkle here:

For example, if the empty obsoletion package is git-completion-4.0

The previous, non-empty version git-completion-3.9 still exists.

Further, this will also keep the corresponding git-src-3.9 package in 
the release.

When you upload git-4.1, you either need to remember to remove 
git-completion-3.9, which will allow git-src-3.9 will be removed, or 
create an empty, obsoletion git-completion-4.1 as well.

This is something which should be done automatically, but isn't.

Re: Process for retiring a subpackage

[Adam Dinwoodie]

On Thu, Mar 17, 2016 at 10:46:53AM -0500, Yaakov Selkowitz wrote:
> On 2016-03-17 07:04, Adam Dinwoodie wrote:
> >Per previous discussion on this list, I'm planning on retiring the
> >separate packaging of Bash completion scripts in the packages I
> >maintain, and folding the files into the main package.  I can't find any
> >documentation that'll hold my hand through that process, so can somebody
> >with the relevant arcane knowledege check my understanding of what's
> >necessary?
> >
> >Taking git-completion as an example, where I'm moving all the contents
> >from that package into the main git package:
> >
> >- For the first release that obsoletes git-completion:
> >
> >   - Create the main git package in such a way that it contains the files
> >     that would previously have been in git-completion.
> >
> >   - Create a dummy git-completion package that:
> 
> Simpler:
> 
> git_OBSOLETES="git-completion"
> 
> Just leave this in indefinitely.

Ah, handy!  One thing that's missing, which I suspect is a bug in
Cygport: I'd expect the git-completion package produced after adding
that would have a category of "_obsolete", but I needed to define
git_completion_CATEGORY for that to happen.

Re: Process for retiring a subpackage

[Yaakov Selkowitz]

On 2016-03-18 07:24, Adam Dinwoodie wrote:
> On Thu, Mar 17, 2016 at 10:46:53AM -0500, Yaakov Selkowitz wrote:
>> Simpler:
>>
>> git_OBSOLETES="git-completion"
>>
>> Just leave this in indefinitely.
>
> Ah, handy!  One thing that's missing, which I suspect is a bug in
> Cygport: I'd expect the git-completion package produced after adding
> that would have a category of "_obsolete", but I needed to define
> git_completion_CATEGORY for that to happen.

No, that's not necessary, cygport handles that just fine.  Did you 
forget to remove git-completion from PKG_NAMES?

-- 
Yaakov

Re: Process for retiring a subpackage

[Adam Dinwoodie]

On Fri, Mar 18, 2016 at 12:45:01PM -0500, Yaakov Selkowitz wrote:
> On 2016-03-18 07:24, Adam Dinwoodie wrote:
> >On Thu, Mar 17, 2016 at 10:46:53AM -0500, Yaakov Selkowitz wrote:
> >>Simpler:
> >>
> >>git_OBSOLETES="git-completion"
> >>
> >>Just leave this in indefinitely.
> >
> >Ah, handy!  One thing that's missing, which I suspect is a bug in
> >Cygport: I'd expect the git-completion package produced after adding
> >that would have a category of "_obsolete", but I needed to define
> >git_completion_CATEGORY for that to happen.
> 
> No, that's not necessary, cygport handles that just fine.  Did you
> forget to remove git-completion from PKG_NAMES?

...

Yes

Oops

Thank you!