From: Maxime Devos <maximedevos@telenet.be>
To: muradm <mail@muradm.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: usage of basu as requirement for sd-bus
Date: Tue, 30 Aug 2022 12:03:18 +0200 [thread overview]
Message-ID: <3650eac3-fff4-8493-81c1-4750eff3d23f@telenet.be> (raw)
In-Reply-To: <87tu5ukr3i.fsf@muradm.net>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 2447 bytes --]
On 30-08-2022 11:27, muradm wrote:
>>
>> IIUC, everything using basu also works fine with elogind (*), so the
>> 'status quo' of still using elogind (for old and new) seems harmless
>> to me (except for size -- basu is smaller).
>
> I don't find the "everything using basu also works fine with elogind"
> statement/assumption/guess correct, as per contents of elogind and
> basu. See above comment for ifdef thingy.
From the README.md of basu:
> The sd-bus library, extracted from systemd. Agreed on th
>
> Some projects rely on the sd-bus library for DBus support. However not all
> systems have systemd or elogind installed. This library provides just
> sd-bus
> (and the `busctl` utility).
This does not look like basu adds additional functionality.
> My intention is not to have something that is not used. Roughly, if
> elogind is not used, why should I have it on my system.
You should have it because the alternative (i.e., sometimes using basu
and sometimes using elogind) increases disk space usage -- it's all
internal, unless there's a bug you shouldn't notice it's using elogind
instead of basu unless you're doing "guix edit" or such.
> Basically,
>
> elogind provides: elogind, loginctl, busctl, libelogind (sd-bus,
> sd-login ...) ...
> basu provides: busctl, libbasu
>
> If basu is enought for package it should dependen on basu IMHO.
>
> So my reason is not directly-storage-only, but dependency which
> impacts storage in some or another way.
We have package outputs, we can separate the libelogind and busctl from
the rest. elogind is used, just not in its entirety.
> Btw, how much storage are we talking about when having some
> packages depend on elogind and some on basu? Is it user
> storage or build server/substitute storage concern?
For basu and elogind itself: 0.9 MiB and 4.2 MiB
For basu and elogind in total: 72.9 MiB and 172.8 MiB.
(See: "guix size").
The latter numbers are a bit misleading, as one of the dependencies is
'shepherd' and 'libgc', which would be installed anyway by other
software, and because elogind refers to pkg-config while it probably
shouldn't.
On "Is it user storage or build serve/substitute storage concern": yes.
There isn't really a "user / substitute storage" distinction, unless you
count baked nars. But that's just multiplying the storage by approx. 2
(ignoring deduplication).
Greetings,
Maxime.
[-- Attachment #1.1.1.2: Type: text/html, Size: 3636 bytes --]
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-08-30 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 7:59 usage of basu as requirement for sd-bus muradm
2022-08-30 9:12 ` Maxime Devos
2022-08-30 9:13 ` Maxime Devos
2022-08-30 9:27 ` muradm
2022-08-30 10:03 ` Maxime Devos [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=3650eac3-fff4-8493-81c1-4750eff3d23f@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=mail@muradm.net \
/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).