From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] babl
Date: Tue, 26 May 2020 17:33:02 +0200 [thread overview]
Message-ID: <172bd3de-b15d-a1bc-cef6-0d7444617dc7@gmail.com> (raw)
In-Reply-To: <df25ce1e-5b2b-c769-e18a-0243575f0431@cornell.edu>
On 26.05.2020 00:18, Ken Brown via Cygwin-apps wrote:
> cygport file and patches attached.
>
> The build system has changed from autotools to meson. The former is no
> longer supported.
>
> I have disabled gobject introspection for reasons explained here:
>
> https://sourceware.org/pipermail/cygwin-apps/2020-May/040093.html
>
> This represents no change, because Yaakov disabled it (for different
> reasons) several years ago. I'm hoping to be able to re-enable it at
> some point.
>
> I went to some trouble, with the help of Jon Turney, to make the html
> docs build, so I packaged them in a (new) libbabl-doc package. Is there
> any reason not to do this?
>
> Fedora packages the docs also, in babl-devel-docs.
>
> Ken
changed maintainer
prev parent reply other threads:[~2020-05-26 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 22:18 Ken Brown
2020-05-26 15:33 ` Marco Atzeri [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=172bd3de-b15d-a1bc-cef6-0d7444617dc7@gmail.com \
--to=marco.atzeri@gmail.com \
--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).