From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: Dedup x86/x86_64 --> noarch
Date: Mon, 09 May 2016 22:41:00 -0000 [thread overview]
Message-ID: <p442jbp4sn1nrj1t8umrmsne9jtk6arc2p@4ax.com> (raw)
In-Reply-To: <87zistg99v.fsf@Rainer.invalid>
> After a discussion on IRC about de-duping the noarch content out of
> package files (where I was told this would be too difficult), I've just
> tried what would happen for two of my packages, maxima and perl.
I feel as though I've once again missed some important discussion about package
maintenance. Your question implies that we can now upload packages with arch
"noarch". Is that true?
I remember a discussion of this question a year or two ago, where IIRC the
result was that we wouldn't have any "noarch" packages. Did that change? If
so, I seem to have missed the discussion here. It should be worth a "HEADSUP".
If this is what's happened, we need to update https://cygwin.com/setup.html with
the new information (the page is overdue for an overhaul anyway). In particular
I wonder if cygport is ready to handle the change.
Or, maybe I'm just misunderstanding.
Thanks,
Andrew
next prev parent reply other threads:[~2016-05-09 22:41 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
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 [this message]
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=p442jbp4sn1nrj1t8umrmsne9jtk6arc2p@4ax.com \
--to=schulman.andrew@epa.gov \
--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).