From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 00/10] Various setup patches
Date: Thu, 04 Aug 2016 11:40:00 -0000 [thread overview]
Message-ID: <20160804114049.GF25811@calimero.vinschen.de> (raw)
In-Reply-To: <87vazhsk8w.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
On Aug 3 21:52, Achim Gratz wrote:
> Corinna Vinschen writes:
> >> People tend to not re-install their whole set of packages just because
> >> some new version of setup is announced,
> >
> > Uhm? If you download a new setup, but then don't update your packages,
> > why did you download the latest setup at all? If you don't run this
> > new setup, you won't get new-style files.
>
> The checksum information has to come from somewhere and that somewhere
> requires a package install or update. Together with that new setup we might
> have an update of cygccheck and some unrelated packages that happen to
> have been rebuilt recently, but certainly not the whole distribution.
Why is that important? The checksums will collect over time.
> >> so I'm going to assume that for
> >> quite some time a mix of old and new .lst files (for instance) exists on
> >> the majority of installations and whatever we do (in cygcheck, say)
> >> needs to work with that.
> >
> > 1. Provide new versions of cygwin, cygcheck-dep and _autorebase
> > 2. time passes (2 weeks or so)
> > 3. Provide a new version of setup
>
> That doesn't cut it, unless you want to require the whole distribution
> to be rebuilt and everything re-installed with that change. Cygwin10
> 1609 or something like that? :-)
I don't think I understand what you're up to. Why is it important
to add the extra information all at once? And if that's the case,
couldn't we use a runonce postinstall script for that?
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-08-04 11:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 15:31 Jon Turney
2016-08-02 15:31 ` [PATCH setup 04/10] Downgrade "Running preremove script" logging to debug Jon Turney
2016-08-02 15:31 ` [PATCH setup 06/10] Remove obsolete installed_from member from packagemeta Jon Turney
2016-08-02 15:31 ` [PATCH setup 10/10] Reserve paths starting "." for package metadata Jon Turney
2016-08-02 15:31 ` [PATCH setup 05/10] Properly report progress in PrereqChecker::isMet Jon Turney
2016-08-02 15:31 ` [PATCH setup 02/10] Prevent libtool warning that a getopt++ shared library cannot be built Jon Turney
2016-08-02 15:31 ` [PATCH setup 03/10] Add lex and yacc generated files to .gitignore Jon Turney
2016-08-02 15:31 ` [PATCH setup 09/10] Add an additional filter view, showing packages which were user picked Jon Turney
2016-08-02 15:31 ` [PATCH setup 07/10] Remove unused fn member from cygpackage Jon Turney
2016-08-02 15:31 ` [PATCH setup 01/10] Remove stray execute permissions Jon Turney
2016-08-02 15:31 ` [PATCH setup 08/10] Track if a package was installed by user, or as a dependency Jon Turney
2016-08-03 10:49 ` Jon Turney
2016-08-03 7:10 ` [PATCH setup 00/10] Various setup patches Achim Gratz
2016-08-03 8:35 ` Corinna Vinschen
2016-08-03 9:52 ` Achim Gratz
2016-08-03 17:40 ` Corinna Vinschen
2016-08-03 18:28 ` Achim Gratz
2016-08-03 18:43 ` Corinna Vinschen
2016-08-03 19:52 ` Achim Gratz
2016-08-04 11:40 ` Corinna Vinschen [this message]
2016-08-04 17:57 ` Achim Gratz
2016-08-04 18:00 ` Corinna Vinschen
2016-08-04 19:26 ` Achim Gratz
2016-08-03 17:30 ` Corinna Vinschen
2017-05-23 16:46 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=20160804114049.GF25811@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).