unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Edouard Klein <edk@beaver-labs.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: What to do when udpating a package ?
Date: Fri, 15 May 2020 18:17:01 +0200	[thread overview]
Message-ID: <CAJ3okZ3fX9ksz__L1k7PoPN8W4r9je6SijRVuYCaMv5r348FHA@mail.gmail.com> (raw)
In-Reply-To: <87mu696w6w.fsf@alice.lan>

On Fri, 15 May 2020 at 17:43, Edouard Klein <edk@beaver-labs.com> wrote:

> I could not find the link to the raw log, but having access to the
> "official" build status is a huge relief, as I can stop worrying that
> the build failure is my fault. This is exactly what I was looking for.
> Thank you !

I have cheated a bit because with this example, there is not raw -- I
do not know why.  But you get the principle. :-)


> >>   --> Is there a way to check the graph to make the edges as
> >>       sparse as possible (i.e. remove as many edges as possible without
> >>       changing the reachability) ? Would this be something we want ?
> >>       According to me it would because it would make the packages
> >>       definitions shorter and the computations on the graph faster, but I'm
> >>       not sure.
> >
> > What do you mean by "reachability"?
> > There is a new feature to "guix graph": '--path'.  You can find the
> > shortest path from one package to another, e.g.,
> >
> >   guix graph --path guix-jupyter python
> >
> > What do you mean by "the edges as sparse as possible"?
> >
> >
> So if A depends on B and C, and B also depends on C, which is preferable
> as far as explicit input declarations in the packages code go:
> --

(1)
> A->B;
> B->C;

(2)
> A->B;
> A->C;
> B->C;

If A depends on B *and* C, then (1) should not work.
Well, it depends on how A depends* on C and what C propagates.
If I understand correctly.

*build-time or runtime.


> The reachability (in the graph theoretical sense
> https://en.wikipedia.org/wiki/Reachability) is the same, but one graph
> has one edge less and is thus "minimal". If I understood Julien correctly he seems to think
> that the fully connected case is better (easier maintainability).

Well, does "guix graph --path" cover your expectation about reachability?
Because "guix graph --path" computes the shortest path -- graph theory
meaning -- from s to t.  So if the path is not empty, then t is
reachable from s.


All the best,
simon


      reply	other threads:[~2020-05-15 16:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  7:20 What to do when udpating a package ? Edouard Klein
2020-05-15 12:26 ` Julien Lepiller
2020-05-15 15:32   ` Edouard Klein
2020-05-15 15:45     ` Julien Lepiller
2020-05-15 13:36 ` zimoun
2020-05-15 15:43   ` Edouard Klein
2020-05-15 16:17     ` zimoun [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=CAJ3okZ3fX9ksz__L1k7PoPN8W4r9je6SijRVuYCaMv5r348FHA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=edk@beaver-labs.com \
    --cc=guix-devel@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.
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).