From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: What about dependency resolution à la apt?
Date: Fri, 17 Mar 2017 02:07:47 -0700 [thread overview]
Message-ID: <87shmcnue4.fsf@gmail.com> (raw)
In-Reply-To: <8737ecu94a.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 16 Mar 2017 23:53:09 +0100")
[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Howdy Amirouche!
>
> Amirouche <amirouche@hypermove.net> skribis:
>
>> Le 16/03/2017 à 21:28, Tobias Geerinckx-Rice a écrit :
>>> Amirouche,
>>>
>>> On 16/03/17 19:52, Amirouche wrote:
>>>> Héllo,
>>> Hi!
>>>
>>> I'm not the most technically qualified person to answer this, nor the
>>> most articulate, but I'm mainly curious and slightly puzzled as to why
>>> this question keeps popping up.
>>
>> Sorry!
>
> No problem, there’s nothing wrong with your question.
>
> The key point in Tobias’ message is this:
>
>>> But one of the many great things about functional package management à
>>> la Nix/Guix is that you don't need — or want — a dependency resolver. At
>>> all. That eliminates a lot of nasty problems, and makes others much
>>> easier to solve.
>
> Tools like apt allow developers to describe a (very large) set of
> possible dependency graphs, which the dependency resolver tries hard to
> narrow down to something reasonable.
>
> Conversely, functional package managers describe just one dependency
> graph. The downside is the “security update” scenario, though we
> address it with grafts¹, and the huge advantage is that we get tractable
> build processes and package composition.
>
> HTH!
>
> Ludo’.
>
> ¹ https://gnu.org/s/guix/news/timely-delivery-of-security-updates.html
Amirouche, your question is a perfectly natural one to ask. If you're
hungry for additional information regarding this interesting topic,
consider reading the introduction to Eelco Dolstra's Nix thesis [1]. In
the first 17 pages, he describes the main issues in the field of
software deployment, surveys the state of the art (as of August 2006)
while pointing out the unsolved problems, and summarizes how Nix (and
thus Guix, which uses Nix) solves those problems.
Section 1.2 is of particular interest. In it, Eelco explains why the
practice of specifying dependencies by name (even when a version is
included) is insufficient for correct deployment of software.
[1] https://nixos.org/%7Eeelco/pubs/phd-thesis.pdf
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-03-17 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 18:52 What about dependency resolution à la apt? Amirouche
2017-03-16 20:28 ` Tobias Geerinckx-Rice
2017-03-16 20:29 ` Thompson, David
2017-03-16 20:31 ` Tobias Geerinckx-Rice
2017-03-16 20:56 ` Amirouche
2017-03-16 22:45 ` Tobias Geerinckx-Rice
2017-03-16 22:53 ` Ludovic Courtès
2017-03-17 9:07 ` Chris Marusich [this message]
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=87shmcnue4.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.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.
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).