From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: setup 2.885 release candidate - please test
Date: Tue, 30 Jan 2018 18:49:00 -0000 [thread overview]
Message-ID: <87zi4vdvwk.fsf@Rainer.invalid> (raw)
In-Reply-To: <874ln4cw15.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 29 Jan 2018 20:19:50 +0100")
Achim Gratz writes:
>> - Add support for 'depends2: package (relation version) [...]', in a
>> version section in setup.ini
>
> Those lines don't seem to get generated for all packages yet. I
> currently merge with requires: to produce a working setup.ini re-write
> and will switch to using requires: when I find no depends2:. Can I
> assume that all versions have a depends2: line when I find one for
> [curr]?
…and of course these are a result of the latest officially available
calm version not having those changes, so my local packages are still
using requires: lines. Any chance you could relese a new calm version?
Other than that I think I've fixed up my setup rewriter so it can deal
with the new format correctly now and I've even managed to implement
explicit version pinning (which I had on TODO for almost three years,
but since before I've only had test, curr and prev for testing I've put
it up each time I looked at it).
Another thing I noticed today is that when packages get upgraded the
transaction list that gets printed to the console seems to always show
the removal of the old package _after_ the installation of the new
version. I guess that will not happen in this order, but it looks
positiviely wierd on screen.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2018-01-30 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 18:11 Jon Turney
2018-01-29 19:20 ` Achim Gratz
2018-01-30 18:49 ` Achim Gratz [this message]
2018-01-30 20:19 ` Jon Turney
2018-01-30 21:13 ` Achim Gratz
2018-01-31 17:48 ` Jon Turney
2018-01-30 20:18 ` Jon Turney
2018-01-31 17:48 ` Jon Turney
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=87zi4vdvwk.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).