From: "amano.kenji" <amano.kenji@proton.me>
To: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Direct symlink farm for transitive dependencies vs search paths
Date: Wed, 18 Sep 2024 01:41:36 +0000 [thread overview]
Message-ID: <GymIQ-a1jxBj5TxSdkcOsc98e2CiKiv_QCKBnFZwuQ8PVJTl1-_msL0hnhqcPAk7FiR3a6hnguh6J3S6JPCZcmTfZqpudpg9KdfD6NuEjTM=@proton.me> (raw)
Let's say that A depends on B, and B depends on C.
With search paths, A doesn't have symlinks to B, and B doesn't have symlinks to C. Thus, disk space is saved.
However, adding search path patches to existing softwares is cumbersome, and a long list of search paths results in inefficient searches.
Let's assume that B has symlinks to C, and A has symlinks to everything in B. This means A has symlinks to symlinks in B. Transitive symlink is probably more efficient than search path. If A just copies symlinks from B and has symlinks to plain files in B, then A ends up with only direct symlinks. Direct symlinks are more efficient than transitive symlinks.
It seems that search paths are preferred over symlinks to transitive dependencies in gnu guix. Why?
next reply other threads:[~2024-09-18 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 1:41 amano.kenji [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-18 5:49 Direct symlink farm for transitive dependencies vs search paths Adam Faiz
2024-09-18 8:10 ` amano.kenji
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='GymIQ-a1jxBj5TxSdkcOsc98e2CiKiv_QCKBnFZwuQ8PVJTl1-_msL0hnhqcPAk7FiR3a6hnguh6J3S6JPCZcmTfZqpudpg9KdfD6NuEjTM=@proton.me' \
--to=amano.kenji@proton.me \
--cc=help-guix@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).