From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Dedup x86/x86_64 --> noarch
Date: Sat, 23 Apr 2016 15:43:00 -0000 [thread overview]
Message-ID: <87mvoknxew.fsf@Rainer.invalid> (raw)
In-Reply-To: <20160423153230.GK15916@calimero.vinschen.de> (Corinna Vinschen's message of "Sat, 23 Apr 2016 17:32:30 +0200")
Corinna Vinschen writes:
> The src packages would ideally be in a src subdir, parallel to the
> noarch and $arch dirs.
Hmm, I'm not soure I'd like that.
The src packages are not generally arch-less. There are several
examples where either the cygport files, the patches or even the source
archives are arch-specific. Of these, the .cygwin patches are almost
certainly spurious since they get time-stamped on creation. The other
differences most likely aren't, although it should be possible to
reconcile them in most cases.
On another note, it still irks me that the debuginfo packages aren't
following the naming convention of the src packages; they should be
named ${PKG}-${PVR}-debuginfo.tar.xz and treated with their respective
box in setup.exe just like the sources.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2016-04-23 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 10:04 Achim Gratz
2016-04-18 19:45 ` Achim Gratz
2016-04-23 10:51 ` Jon Turney
2016-04-23 11:19 ` Achim Gratz
2016-04-23 14:19 ` Achim Gratz
2016-04-23 15:32 ` Corinna Vinschen
2016-04-23 15:43 ` Achim Gratz [this message]
2016-05-09 14:38 ` Jon Turney
2016-05-09 16:43 ` Achim Gratz
2016-05-09 14:18 ` Jon Turney
2016-05-09 16:45 ` Achim Gratz
2016-05-09 22:41 ` Andrew Schulman
2016-05-10 5:44 ` Achim Gratz
2016-05-10 6:20 ` Andrew Schulman
2016-05-11 18:59 ` 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=87mvoknxew.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).