From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104432 invoked by alias); 18 Mar 2016 12:24:28 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 104400 invoked by uid 89); 18 Mar 2016 12:24:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-wm0-f45.google.com Received: from mail-wm0-f45.google.com (HELO mail-wm0-f45.google.com) (74.125.82.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 18 Mar 2016 12:24:11 +0000 Received: by mail-wm0-f45.google.com with SMTP id l68so66380805wml.0 for ; Fri, 18 Mar 2016 05:24:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=VIAZepn6vDhe09sboKlu3Fxj7+V5cQDDsu8DgqxdcPI=; b=OyMk5I529ZPzcCrp2ynVBjs1iOGvnal8eTXdI0YyeZuPwyhr+uXfuuG+rpCsV+93Nd gf+6CW9Xidq2yuVc22B7FDMk3Z9EtLZ4dAMlLYGqoBARLTriSxBztr7b9bwktJZrKc3A aOUp7EpD8/kNQQ3KktOe6zWMCDkMUCtETQNx8BbqkiWf9zbp595q1N17y50vv7/2hJn0 m+Y+CZ0c6KB07dg/4tUfJt1ZkHlnARC5vJkF9NiMFKqYJ+rOxcxGtcJWX0/UEHFfNHnJ tPmAfpoXYRjPydQDycLPQp2wnqCcm0yBfZpxO1u5iNNmsvoqS6s1KXtDlXEe9Im/lDCo QISA== X-Gm-Message-State: AD7BkJIMke4iTF5dQoT3XfVC2crZZ0/3p0R+iWxMlv/New0p6mvWuhVrkSQPB/trv+EecQ== X-Received: by 10.28.227.69 with SMTP id a66mr40853578wmh.57.1458303848954; Fri, 18 Mar 2016 05:24:08 -0700 (PDT) Received: from dinwoodie.org ([2001:ba8:0:1c0::9:1]) by smtp.gmail.com with ESMTPSA id v188sm34358345wmv.3.2016.03.18.05.24.07 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 18 Mar 2016 05:24:07 -0700 (PDT) Date: Fri, 18 Mar 2016 12:24:00 -0000 From: Adam Dinwoodie To: cygwin-apps@cygwin.com Subject: Re: Process for retiring a subpackage Message-ID: <20160318122406.GB29016@dinwoodie.org> References: <20160317120414.GT29016@dinwoodie.org> <56EAD16D.70003@cygwin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56EAD16D.70003@cygwin.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2016-03/txt/msg00072.txt.bz2 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.