From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61624 invoked by alias); 9 Oct 2017 19:33:25 -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 61609 invoked by uid 89); 9 Oct 2017 19:33:25 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=BAYES_20,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=packaged, H*Ad:D*gov, complicated, H*r:Unknown X-HELO: blaine.gmane.org Received: from Unknown (HELO blaine.gmane.org) (195.159.176.226) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 09 Oct 2017 19:33:24 +0000 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1e1dnc-0006v3-5m for cygwin-apps@cygwin.com; Mon, 09 Oct 2017 21:33:12 +0200 To: cygwin-apps@cygwin.com From: Andrew Schulman Subject: Re: [PATCH cygport] Add a command to make a test release Date: Mon, 09 Oct 2017 19:33:00 -0000 Message-ID: References: <4nectcp0vd3dvhn5rh5ed0h3difc47jedm@4ax.com> <4nectcp0vd3dvhn5rh5ed0h3difc47jedm-e09XROE/p8c@public.gmane.org> <0f58e59c-2953-b7d2-98d6-de8f2bcd2da1@cornell.edu> <87wp471jl0.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes X-SW-Source: 2017-10/txt/msg00048.txt.bz2 > Andrew Schulman writes: > > Ooh, how about this: > > > > cygport lftp.cygport all > > cygport lftp.cygport override curr=4.7.7-1 test=4.7.8-1 > > cygport lftp.cygport up > > > > That would create override.hint and upload it with the package, leaving the > > cygport file and source package alone. > > The command line parsing in cygport would become a lot more complicated > for starters, so the syntax should be different. > > But more to the point, some people want to do this on the command line, > while others do not. I for one don't want to do it from the command > line because I have oodles of packages that I build semi-automatically > and changing the commands issued for each individual package just > doesn't work well for me. So I do want this to be part of the file set > I commit to my Git repository instead (yes, if forced I could wrap > another layer of scripting or cygport patches around it). In other > words, in the end we likely need to have both. That's fine. > A separate issue is if those things should end up in the package > archives. I agree that often they should not, so again my suggestion is > to record this simply in a separate file that does not get packaged and > (as outlined above) to provide means to create the same effects from the > command line. Agree. The idea is that cygport can create override.hint, or the packager can create it. Then cygport uploads it along with the package files. But it's a separate file, not part of the package archive.