From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: Dedup x86/x86_64 --> noarch
Date: Mon, 09 May 2016 14:38:00 -0000 [thread overview]
Message-ID: <c44367f6-466a-ae50-e6e9-6b6f3e866d2a@dronecode.org.uk> (raw)
In-Reply-To: <87mvoknxew.fsf@Rainer.invalid>
On 23/04/2016 16:43, Achim Gratz wrote:
> Corinna Vinschen writes:
>> The src packages would ideally be in a src subdir, parallel to the
>> noarch and $arch dirs.
>
> Hmm, I'm not sure 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.
I think 'generally' is over-stating the case, the vast majority of
source packages should be arch-less.
If the source package really is arch-specific, then it should be marked
so with ARCH [1]
If it contains arch-specific patches, they should be made conditional on
ARCH.
[1] https://cygwinports.github.io/cygport/compilers_cygpart.html#robo872
> 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.
But yes, this is not straightforward because the way we generate source
packages at the moment means there is no guarantee that the same source
package is used to build the different arch variants.
> 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.
We have the source code :)
next prev parent reply other threads:[~2016-05-09 14:38 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
2016-05-09 14:38 ` Jon Turney [this message]
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=c44367f6-466a-ae50-e6e9-6b6f3e866d2a@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).