From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Add a command to make a test release
Date: Mon, 09 Oct 2017 19:33:00 -0000 [thread overview]
Message-ID: <kljntcd3ai3iu259s5d1nsklkpq76cj8o0@4ax.com> (raw)
In-Reply-To: <87wp471jl0.fsf@Rainer.invalid>
> 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.
next prev parent reply other threads:[~2017-10-09 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 19:51 Jon Turney
2017-10-03 20:01 ` Andrew Schulman
2017-10-03 20:25 ` Achim Gratz
2017-10-05 12:24 ` Jon Turney
2017-10-05 14:23 ` Andrew Schulman
2017-10-05 16:57 ` Ken Brown
2017-10-05 19:50 ` Andrew Schulman
2017-10-07 7:52 ` Achim Gratz
2017-10-09 19:33 ` Andrew Schulman [this message]
2017-10-05 18:16 ` Achim Gratz
2017-10-05 19:33 ` cyg Simple
2017-10-05 18:14 ` Achim Gratz
2017-11-01 19:58 ` Yaakov Selkowitz
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=kljntcd3ai3iu259s5d1nsklkpq76cj8o0@4ax.com \
--to=schulman.andrew@epa.gov \
--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).