From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: "Åke Rehnman" <ake.rehnman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [ITP] libftdi1 & libconfuse
Date: Wed, 19 Apr 2017 15:52:00 -0000 [thread overview]
Message-ID: <c47a964a-065c-6777-05d3-e7a7e87b387b@dronecode.org.uk> (raw)
In-Reply-To: <afa43f96-dcb6-4372-6b9f-70ca1400f7b3@gmail.com>
On 18/04/2017 19:50, Ã
ke Rehnman wrote:
> Hello all,
>
> One more effort to try getting some attention towards libftdi and
> libconfuse packages...
Thank you for your patience and sorry about the delay.
> Both libftdi and libconfuse are available in ubuntu and debian + others.
> Libftdi is used with openocd among others. Libconfuse is used by eeprom
> programmer for libftdi.
>
> libftdi1 is released under LGPL 2.1 and eeprom programmer under GPL 2.
> See https://www.intra2net.com/en/developer/libftdi/index.php
>
> libconfuse is released under ISC License. See
> https://github.com/martinh/libconfuse/blob/master/LICENSE
>
[..]
>
> Files available here: https://stm8-binutils-gdb.sourceforge.io/cygwin/
libftdi1.cygport should use 'DEPEND=pkgconfig(libconfuse)' rather than
hand-rolling a check for it.
I guess that it should also have 'pkgconfig(libusb-1.0) swig'.
With those things fixed, package looks good, so please provide a ssh key
as per https://cygwin.com/package-upload.html
next prev parent reply other threads:[~2017-04-19 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 12:33 [ITP] libftdi1 Åke Rehnman
2017-04-18 18:50 ` [ITP] libftdi1 & libconfuse Åke Rehnman
2017-04-19 15:52 ` Jon Turney [this message]
2017-04-19 22:03 ` Åke Rehnman
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=c47a964a-065c-6777-05d3-e7a7e87b387b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=ake.rehnman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--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).