public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] moreutils 0.61
Date: Mon, 20 Nov 2017 17:20:00 -0000	[thread overview]
Message-ID: <88b9a5cb-459a-25e3-b8e9-341bf07d7601@dronecode.org.uk> (raw)
In-Reply-To: <20171116150816.GL20681@dinwoodie.org>

On 16/11/2017 15:08, Adam Dinwoodie wrote:
> On Wednesday 15 November 2017 at 08:52 pm +0000, Tony Kelman wrote:
>>>>>> -   parallel: run multiple jobs at once
> 
> 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.

I'm pretty sure already have some undiagnosed conflicts like this 
already, so a potential future one isn't any great impairment.

Marking packages as mutually conflicting is perhaps within reach, as 
it's something that would be relatively straightforward with 
libsolv-based setup.

Automatically detecting such packages is more work, but something that 
could also be done.

> -   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

Yeah, laziness and inertia solve all problems, because if you wait long 
enough, the problems go away :)

  parent reply	other threads:[~2017-11-20 17:20 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
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 [this message]
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=88b9a5cb-459a-25e3-b8e9-341bf07d7601@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).