From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Process for retiring a subpackage
Date: Thu, 17 Mar 2016 14:05:00 -0000 [thread overview]
Message-ID: <20160317140524.GD3302@calimero.vinschen.de> (raw)
In-Reply-To: <20160317120414.GT29016@dinwoodie.org>
[-- 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 --]
next prev parent reply other threads:[~2016-03-17 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 12:04 Adam Dinwoodie
2016-03-17 14:05 ` Corinna Vinschen [this message]
2016-03-17 15:46 ` Yaakov Selkowitz
2016-03-17 16:08 ` Jon Turney
2016-03-18 12:24 ` Adam Dinwoodie
2016-03-18 17:45 ` Yaakov Selkowitz
2016-03-18 21:02 ` Adam Dinwoodie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160317140524.GD3302@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).