Message ID | 20220401204441.8244-1-kevinboulain@gmail.com |
---|---|
Headers | show |
Series | gnu: linux: update PipeWire & WirePlumber | expand |
Kevin Boulain schreef op vr 01-04-2022 om 22:44 [+0200]: > I assume you mean ./pre-inst-env guix size pipewire? > store item total self > [...] > Do you need the full output (where should I paste it)? More concretely, I'm wondering what the impact is of the new inputs: + libfdk + libsndfile + libusb + lilv + openssl + readline + webrtc-audio-processing What are their 'total self percentage' values? Greetings, Maxime.
Kevin Boulain schreef op vr 01-04-2022 om 22:44 [+0200]: > I've no idea how that works on Guix, I assume it's not as simple as with other > distributions where all libraries/plugins can be found in a single place (/lib). > Do you have an example? Maybe have a look at how audacity searches AUDACITY_MODULE_PATH and 'dlopen's things? Or BASH_LOADABLES_PATH. Greetings, Maxime.
On Sat, 2 Apr 2022 at 18:19, Maxime Devos <maximedevos@telenet.be> wrote: > More concretely, I'm wondering what the impact is of the new inputs: > [...] > What are their 'total self percentage' values? Right, so just to make sure we're on the same page: - guix size pipewire before this patch: https://paste.debian.net/hidden/57a05080/ - guix size pipewire after this patch: https://paste.debian.net/hidden/cbb93545/ - diff: https://paste.debian.net/hidden/3cb51fbd/ Surprisingly there isn't that much of an increase (~5MiB). That's because most of the new dependencies were already pulled in by existing dependencies. For example, PulseAudio was pulling libsndfile & webrtc-audio-processing. Bluez was pulling readline. I traced one OpenSSL use back to a ffmpeg plugin dependency (rav1e's rust-cargo-c, it's also used by other things but the Graphviz graph is too big to generate a visualization). This leaves us with only these new dependencies (see diff): libfdk-2.0.1 75.2 3.5 0.4% libusb-1.0.24 72.1 0.4 0.0% lilv-0.24.12 74.0 0.3 0.0% serd-0.30.8 71.9 0.2 0.0% sord-0.16.8 73.7 0.1 0.0% sratom-0.6.6 73.7 0.1 0.0%
Kevin Boulain schreef op za 02-04-2022 om 20:33 [+0200]: > Surprisingly there isn't that much of an increase (~5MiB). That's > because most of the new dependencies were already pulled in by > existing dependencies. Ok, that doesn't seem too bad. Greetings, Maxime.
Friendly ping: what's the status of these patches? Are we waiting to see if the extra functionaly can be provided as separate plug-in packages so they won't clutter up the dependency graph? Thanks, Jack
On 18-08-2022 22:46, Jack Hill wrote: > Friendly ping: what's the status of these patches? Are we waiting to > see if the extra functionaly can be provided as separate plug-in > packages so they won't clutter up the dependency graph? AFAIK, no, it would be useful but AFAIK not a blocker. AFAIK the only thing we are waiting for is for someone to commit the patches. Though as a reminder, I only looked at the patches, I didn't check the source diff for various forms of 'badness'. Greetings, Maxime.