public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: Advice needed on ffcall packaging
Date: Tue, 20 Feb 2018 17:26:00 -0000	[thread overview]
Message-ID: <c3910dd0-6ace-d351-de64-607e7d6c51ba@gmail.com> (raw)
In-Reply-To: <c80f89ea-e66f-9673-e5f8-a7f2f220bbd5@cornell.edu>

On 20/02/2018 16:47, Ken Brown wrote:
> A few years ago I adopted ffcall (32-bit only) in order to keep it from 
> disappearing from the distro:
> 
>    https://sourceware.org/ml/cygwin-apps/2015-07/msg00092.html
> 

> 
> But I'm not starting from scratch, and users of the existing ffcall will 
> need the new libffcall-devel.  I can think of two possibilities for 
> handling this:
> 
> A) Pretend that I'm starting from scratch, and deal with the fallout. 
> There probably won't be any, since ffcall is not currently required by 
> any other package.  As far as I know, its only use is that it's a build 
> requirement for clisp, which I maintain.
> 
> B) Make three packages as above, with the source-only package being 
> called libffcall instead of ffcall.  (libffcall is the upstream name 
> anyway.)  I could then make libffcall-devel obsolete ffcall.
> 

> 
> Maybe this is much ado about nothing, but I'd appreciate advice.
> 
> Ken

Both are fine.
B is more in line with current trend in package name but it is
just personal taste.

Regards
Marco

  reply	other threads:[~2018-02-20 17:26 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 [this message]
2018-02-20 18:41 ` Yaakov Selkowitz
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=c3910dd0-6ace-d351-de64-607e7d6c51ba@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).