From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: Dedup x86/x86_64 --> noarch
Date: Wed, 11 May 2016 18:59:00 -0000 [thread overview]
Message-ID: <7e678455-6bd3-0992-57dc-e66e458edae4@dronecode.org.uk> (raw)
In-Reply-To: <8cv2jblkgd2khl5esae0s09kc3731aq9s4@4ax.com>
On 10/05/2016 07:20, Andrew Schulman wrote:
>>> 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).
I agree that page is very bad at communicating the information it needs
to communicate. Perhaps it would be much more helpful if it had a few
examples of .cygport files rather than diving into the minutiae of
setup.hint files.
However, I took a look over it, but I don't see what needs updating for
this particular change. Can you be more specific about what you think
needs updating?
I have updated https://sourceware.org/cygwin-apps/package-upload.html
That didn't actually explain before what to do if you are manually
uploading a noarch package ("if you are doing a manual upload, and your
package is noarch, you'll need to upload to both x86 and x86_64"), so
I'm not sure how to update it for the hopefully more straightforward
present situation ("if you are doing a manual upload, and your package
is noarch, upload to noarch").
prev parent reply other threads:[~2016-05-11 18:59 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
2016-05-10 5:44 ` Achim Gratz
2016-05-10 6:20 ` Andrew Schulman
2016-05-11 18:59 ` Jon Turney [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=7e678455-6bd3-0992-57dc-e66e458edae4@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).