all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: guix-patches--- via <guix-patches@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 46215@debbugs.gnu.org
Subject: [bug#46215] [PATCH] Add yadm
Date: Mon, 01 Feb 2021 10:06:03 +0000	[thread overview]
Message-ID: <a69c6126-5304-48ca-a992-a6a0254e2d84@elken.dev> (raw)
In-Reply-To: <38ed969df583e9254802fa7a4a80299ec5caddc4.camel@student.tugraz.at>

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

I understand that, the question was how are they handled if they're installed after yadm? Would yadm be rebuilt with the new inputs?

On 1 Feb 2021, 08:14, at 08:14, Leo Prikler <leo.prikler@student.tugraz.at> wrote:
>Am Montag, den 01.02.2021, 03:44 +0000 schrieb Ellis Kenyő:
>> Hi Leo,
>>
>> I understand what to do, I just wasn't sure how dependencies
>> installed later would be handled. Some are optional and if they don't
>> exist yadm just carries on, but some are required.
>>
>> Would the optional ones still be handled?
>Guix' policy is to include as many optional dependencies as possible,
>up to a reasonable limit in closure size.  In this case, that's
>hopefully all of them.
>
>Regards,
>Leo

[-- Attachment #2: Type: text/html, Size: 1208 bytes --]

  reply	other threads:[~2021-02-01 10:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 16:47 [bug#46215] [PATCH] Add yadm guix-patches--- via
2021-01-31 17:38 ` Leo Prikler
2021-01-31 20:16   ` guix-patches--- via
2021-01-31 20:36     ` Leo Prikler
2021-02-01  3:44       ` guix-patches--- via
2021-02-01  8:13         ` Leo Prikler
2021-02-01 10:06           ` guix-patches--- via [this message]
2021-02-01 11:44             ` Leo Prikler
2021-02-06 10:05               ` Ellis Kenyő via Guix-patches via
2021-02-06 10:48                 ` Leo Prikler
2021-02-06 10:58                   ` Ellis Kenyő via Guix-patches via
2021-02-06 11:22                     ` Leo Prikler
2021-02-06 11:26                       ` Ellis Kenyő via Guix-patches via
2021-02-06 11:46                       ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-06 12:41                         ` Leo Prikler
2021-02-06 11:30                     ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-06 11:43                       ` Ellis Kenyő via Guix-patches via
2021-02-06 11:58                       ` Leo Prikler
2021-02-06 12:03                         ` Tobias Geerinckx-Rice via Guix-patches via
2022-09-09  0:01 ` [bug#46215] [PATCH] gnu: " kiasoc5 via Guix-patches via

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=a69c6126-5304-48ca-a992-a6a0254e2d84@elken.dev \
    --to=guix-patches@gnu.org \
    --cc=46215@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    --cc=me@elken.dev \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.