From: Andy Li <andy@onthewings.net>
To: cygwin-apps@cygwin.com, Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: adopt and update libatomic_ops and libgc
Date: Tue, 09 May 2017 05:59:00 -0000 [thread overview]
Message-ID: <CAM-5HMu8kMqiSx4sFfEv9Dh0u-W3mt5LYu0XyV6oa=M5GVN=5w@mail.gmail.com> (raw)
In-Reply-To: <314de125-1e1a-a4d6-9301-7aa859908765@SystematicSw.ab.ca>
> On 2017-05-08 05:54, Jon Turney wrote:
>> libatomic_ops.cygport:
>> A comment that we need to correct for this installing it's
>> documentation into usr/share/libatomic_ops, rather that
>> usr/share/doc/libatomic_ops might be nice.
>> This could alternatively be written using a custom src_install which
>> calls cyginstall then moves the directory, which might be less
>> brittle to changes in the file list?
>> This might be an upstream defect if it doesn't respect --docdir?
Right, I've just sent a PR to the upstream to fix it. See
https://github.com/ivmai/libatomic_ops/pull/25
I've included it as a patch in the cygport file, which we can remove
in the next version if the PR is merged.
>> libgc.cygport:
>> DEPEND might be better written pkgconfig(atomic_ops)
>> Again, stuff installed to usr/share/gc/ should probably be moved to
>> usr/share/doc/gc
Similarly, the PR: https://github.com/ivmai/bdwgc/pull/161
>> I note we also have libgc-7.2d-2 as non-source package, which just
>> contains usr/share/doc/Cygwin/libgc.README. That probably needs to
>> be cleaned up by being obsoleted.
What is the procedure of obsoleting packages?
Best regards,
Andy
next prev parent reply other threads:[~2017-05-09 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 12:42 Andy Li
[not found] ` <012a4d1f-6d82-422d-000a-f214a133df56@dronecode.org.uk>
2017-05-08 14:00 ` Brian Inglis
2017-05-09 5:59 ` Andy Li [this message]
2017-05-09 9:52 ` Jon Turney
2017-05-11 14:27 ` Andrew Schulman
2017-05-11 14:34 ` Andy Li
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='CAM-5HMu8kMqiSx4sFfEv9Dh0u-W3mt5LYu0XyV6oa=M5GVN=5w@mail.gmail.com' \
--to=andy@onthewings.net \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).