This is the mail archive of the
mailing list for the Cygwin project.
Re: adopt and update libatomic_ops and libgc
- From: Andy Li <andy at onthewings dot net>
- To: cygwin-apps at cygwin dot com, Jon Turney <jon dot turney at dronecode dot org dot uk>
- Date: Tue, 9 May 2017 13:59:10 +0800
- Subject: Re: adopt and update libatomic_ops and libgc
- Authentication-results: sourceware.org; auth=none
- References: <CAM-5HMv9qbUM-=450K7RG7J_4yQWCTCOM1Hp5AWbAAs6Hb+s0Q@mail.gmail.com> <email@example.com> <314de125-1e1a-a4d6-9301-7aa859908765@SystematicSw.ab.ca>
> On 2017-05-08 05:54, Jon Turney wrote:
>> 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
I've included it as a patch in the cygport file, which we can remove
in the next version if the PR is merged.
>> DEPEND might be better written pkgconfig(atomic_ops)
>> Again, stuff installed to usr/share/gc/ should probably be moved to
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?