From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: setup and colons in filenames
Date: Thu, 26 Oct 2017 17:42:00 -0000 [thread overview]
Message-ID: <87vaj1u7pl.fsf@Rainer.invalid> (raw)
In-Reply-To: <03e94ec4-db88-8997-40a0-1c63b1a010bd@dronecode.org.uk> (Jon Turney's message of "Thu, 26 Oct 2017 17:14:05 +0100")
Jon Turney writes:
> This seems a really odd thing to do, as we've no idea about the
> dependencies of these packages, so installing them is unlikely work
> well.
This particular code path was vetoed from getting thrown out last time I
worked in that area since it would break long-standing expectations
w.r.t. local package archoves that have no setup.ini or even *.hint.
> I'm kind of tempted to remove this mis-feature.
In a properly maintained mirror or local archive it is a mis-feature. I
was told not everyone wants to have to do the extra steps of doing that
maintenance. At least if we detect what should be a proper package repo
we don't additionally look at all the files anymore.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2017-10-26 17:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 15:50 Ken Brown
2017-10-25 19:23 ` Jon Turney
2017-10-25 20:16 ` Corinna Vinschen
2017-10-25 20:36 ` Jon Turney
2017-10-25 21:00 ` Corinna Vinschen
2017-10-26 16:14 ` Jon Turney
2017-10-26 16:14 ` Jon Turney
2017-10-26 17:04 ` Ken Brown
2017-10-26 17:20 ` Jon Turney
2017-10-26 17:42 ` Achim Gratz [this message]
2017-10-26 17:49 ` Jon Turney
2017-10-26 18:25 ` Achim Gratz
2017-10-27 8:47 ` Corinna Vinschen
2017-10-27 10:40 ` Achim Gratz
2017-10-27 13:44 ` Jon Turney
2017-10-27 15:20 ` Ken Brown
2017-10-27 16:28 ` Corinna Vinschen
2017-10-27 13:43 ` 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=87vaj1u7pl.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).