From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Advice needed on ffcall packaging
Date: Tue, 20 Feb 2018 18:41:00 -0000 [thread overview]
Message-ID: <47b9c3bd-2e2c-65e1-2c8b-cf9c35e0ed18@cygwin.com> (raw)
In-Reply-To: <c80f89ea-e66f-9673-e5f8-a7f2f220bbd5@cornell.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1457 bytes --]
On 2018-02-20 09:47, Ken Brown wrote:
> A few years ago I adopted ffcall (32-bit only) in order to keep it from
> disappearing from the distro:
>
> The latest upstream release builds on 64-bit Cygwin, so I'd like to
> update the package, and I'd like to find a sensible way of breaking it
> up into subpackages. Here are the relevant facts:
>
> 1. Cygwin's existing (32-bit) ffcall is really a devel package: It
> consists of headers, four (static) libs, and documentation. There are
> no subpackages and no shared libs.
>
> 2. The build of the current release produces the same four static libs,
> plus shared versions of the first three, plus a new lib, both static and
> shared (libffcall.a and cygffcall-0.dll).
>
> If I were starting from scratch, I would have three packages: ffcall,
> libffcall0, and libffcall-devel. ffcall would be source only;
> libffcall0 would contain the shared libs *.dll; and libffcall-devel
> would contain the headers, the import libs *.dll.a, and the one static
> lib for which there is no shared version. I wouldn't ship the other
> static libs unless I discover later that they're needed for some reason.
>
> But I'm not starting from scratch, and users of the existing ffcall will
> need the new libffcall-devel.
NAME=ffcall
...
PKG_NAMES="libffcall0 libffcall-devel"
libffcall0_CONTENTS=...
libffcall_devel_OBSOLETES="ffcall"
libffcall_devel_CONTENTS=...
--
Yaakov
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-02-20 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 15:48 Ken Brown
2018-02-20 17:26 ` Marco Atzeri
2018-02-20 18:41 ` Yaakov Selkowitz [this message]
2018-02-20 19:24 ` Ken Brown
2018-02-21 5:43 ` Brian Inglis
2018-02-21 14:26 ` Ken Brown
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=47b9c3bd-2e2c-65e1-2c8b-cf9c35e0ed18@cygwin.com \
--to=yselkowitz@cygwin.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).