public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] moreutils 0.61
Date: Thu, 16 Nov 2017 15:08:00 -0000	[thread overview]
Message-ID: <20171116150816.GL20681@dinwoodie.org> (raw)
In-Reply-To: <MWHPR22MB012885C3E181EF4D12022B61A7290@MWHPR22MB0128.namprd22.prod.outlook.com>

On Wednesday 15 November 2017 at 08:52 pm +0000, Tony Kelman wrote:
> >> >> -   parallel: run multiple jobs at once
> >>
> >> I'd be hesitatnt to package that since it directly clashes with GNU
> >> parallel (not available on Cygwin yet).
> >
> > Hmm.  I wasn't aware of GNU parallel, and I'm not sure how that sort of
> > problem is generally handled.  Possibly that could be broken out into a
> > separate package to make it easier for folk to install one or the other?
> > I considered and decided against breaking the entire lot into separate
> > packages, but this is perhaps a good argument for at least separating
> > that.
> 
> This has been a long source of tension between moreutils' author and the
> debian packager (probably fedora and other distros too). I don't know off
> the top of my head what solution those distros have come up with for the
> name conflict but they may be doing something worth investigating and
> imitating.
> 
> I have made frequent use of mispipe and ts, and would probably use other
> pieces of moreutils if I remembered them better, so I'd use and appreciate
> a cygwin package of them - assuming a solution is found to the potential
> name conflict.

It looks like both OS X's Homebrew and Debian's Apt deal with this by
just having the packages conflict.  Homebrew definitely warns about the
conflicts, when it sees you trying to install both packages, and I would
assume Apt does too.

I'm guessing setup-*.exe doesn't have the ability to detect and handle
this sort of conflict, but I can see a bunch of alternative options:

-   Do nothing for now and deal with the problem as and when someone
    ITPs GNU parallel.

-   Add detection for this sort of conflict somehow, and refuse to allow
    users to install conflicting packages.

-   Document the conflict in release announcements but otherwise do
    nothing, and allow the packages to overwrite each other if both are
    installed.

-   Rename moreutils parallel (e.g. `mparallel`) so it doesn't conflict.

-   As and when GNU parallel is packaged, rename it (e.g. `gparallel`)
    so it doesn't conflict.

-   Just refuse to package one or the other for Cygwin.

I'm leaning towards either doing nothing and leaving it as a problem for
the future, or renaming moreutils parallel now, but I'd be very
interested in the list's opinion.

  reply	other threads:[~2017-11-16 15:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 13:10 Adam Dinwoodie
2017-11-15 18:31 ` Achim Gratz
2017-11-15 20:43   ` Adam Dinwoodie
2017-11-15 20:52     ` Tony Kelman
2017-11-16 15:08       ` Adam Dinwoodie [this message]
2017-11-16 15:42         ` Marco Atzeri
2017-11-16 19:50           ` Achim Gratz
2017-11-16 16:34         ` David Stacey
2017-11-16 19:53           ` Achim Gratz
2017-11-16 19:46         ` Achim Gratz
2017-11-20 17:20         ` Jon Turney
2017-11-20 17:19 ` Jon Turney
2017-11-22 14:50   ` Adam Dinwoodie
2017-11-22 15:08     ` Achim Gratz

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=20171116150816.GL20681@dinwoodie.org \
    --to=adam@dinwoodie.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).