From: "Ellis Kenyő via 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: Sat, 06 Feb 2021 10:05:13 +0000 [thread overview]
Message-ID: <87pn1dpkwr.fsf@elken.dev> (raw)
In-Reply-To: <9efaa5895bc488ddd4fd8c456aa5c2fdf09cb4af.camel@student.tugraz.at>
I don't think you're understanding my question.
A number of the dependencies are optional, for example some of the
jinja template commands.
When this builds, if those packages aren't installed before you
install yadm, the path gets set to `#f`.
If you then later install them (one of them for example is a
python module so likely wouldn't be installed through guix), the
path in yadm is still `#f` so it would never find them.
Do I have to also package everything it has a soft dependency on?
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> Am Montag, den 01.02.2021, 10:06 +0000 schrieb Ellis Kenyő:
>> I understand that, the question was how are they handled if
>> they're
>> installed after yadm? Would yadm be rebuilt with the new
>> inputs?
> I think you are fundamentally misunderstanding the nature of
> functional
> package management here. yadm should – like any other package –
> depend
> on its inputs and just its inputs. Whether or not you have
> another
> package installed should not be relevant for the functioning of
> yadm
> and likewise not cause a rebuild. What should cause a rebuild
> is any
> of its inputs changing between two generations of `guix pull'.
>
> Regards,
> Leo
--
Regards,
elken
next prev parent reply other threads:[~2021-02-06 10:10 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
2021-02-01 11:44 ` Leo Prikler
2021-02-06 10:05 ` Ellis Kenyő via Guix-patches via [this message]
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=87pn1dpkwr.fsf@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.