From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Cyclic npm dependencies
Date: Sun, 25 Nov 2018 09:34:58 +0100 [thread overview]
Message-ID: <20181125083457.wxeif4i3fhr2hay7@thebird.nl> (raw)
In-Reply-To: <CAPsKtfKF0yDW9p=udT+Bj91Krz9MRhZeV6H83-V7Fv4zgb6zGg@mail.gmail.com>
On Sat, Nov 24, 2018 at 11:29:08PM +0000, Jelle Licht wrote:
> > So in your example, I imagine an input chain like:
> > node-glob 0.1 -> node-rimraf 0.1 -> node-glob 0.2 ->
> node-rimraf 0.2
> > -> .... -> node-glob 1.0 -> node-rimraf 1.0
> > While *extremely* annoying to untangle, this is definitely
> doable.
> Appears to me that it would suffice to pick the latest version. In
>
> What do you mean? In my specific example, you would need to package
> and build each version in succession in order to actually be able to
> use recent versions of either of these packages. IOW, you can not
> choose any; you need to choose each.
If that is the case there is no way around it. All I am saying you can
start with an 'optimistic' importer and if that fails go back to
resolving the circular depency. I.e., opt for the simple resolution
first.
Arguably a dependency is not circular if versions differ. But that may
be a semantic argument ;)
Pj.
next prev parent reply other threads:[~2018-11-25 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 15:16 Cyclic npm dependencies swedebugia
2018-11-24 15:41 ` Jelle Licht
2018-11-24 16:38 ` Pjotr Prins
2018-11-24 23:29 ` Jelle Licht
2018-11-25 8:34 ` Pjotr Prins [this message]
2018-11-25 13:16 ` swedebugia
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181125083457.wxeif4i3fhr2hay7@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).