From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Setup-x86(_64) (v2.889) ... just a question
Date: Tue, 06 Mar 2018 22:13:00 -0000 [thread overview]
Message-ID: <876068x54b.fsf@Rainer.invalid> (raw)
In-Reply-To: <f07266fe2737c5feae7af41ea5bd68d3@xs4all.nl> (houder@xs4all.nl's message of "Tue, 06 Mar 2018 14:39:47 +0100")
Houder writes:
> Is this the future of setup? Meaning, is it the intention that it may
> be possible that installed.db refers to files that do not exist?
The entries in that file have not been referring to actual file names
for at least a decade if not longer. It's just been kept that way in
order to stay compatible with any known and unknown consumers of that
data. The only real meaning is the _version_ that setup knows to be
installed (the packagename is the first part of the line and just
repeated for the version part that still looks liek a filename).
For setup itself, the file name to be installed doesn't need to match
anything at all (it wouldn't even need a .tar.xz suffix to fihgure out
the file type), but there's a naming convention that gets followed.
It's mostly so that one can look at the install log and understand what
has been installed or more easily find a file to manually install.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2018-03-06 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 13:44 Houder
2018-03-06 14:01 ` Setup-x86(_64) (v2.889) ... just a question (CORRECTION) Houder
2018-03-06 16:27 ` Setup-x86(_64) (v2.889) ... just a question Jon Turney
2018-03-06 17:14 ` Houder
2018-03-06 22:13 ` Achim Gratz [this message]
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=876068x54b.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@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).