I'm sorry, I confused you mentioned term sysroot. It's not about yocto - we just use the same term because it's very similar to how it works into yocto. We got packages as a result of yocto build and use these artefacts (packages) on next stage to populate software components content. For some reason we can't use the same approach with hardlink to deduplicate components content.
Regards, Oleksiy ________________________________ From: Peter Kjellerstedt <[email protected]> Sent: Monday, February 10, 2025 22:05 To: [email protected] <[email protected]>; Oleksiy Obitotskyy -X (oobitots - GLOBALLOGIC INC at Cisco) <[email protected]> Cc: Ross Burton <[email protected]>; [email protected] <[email protected]>; Ruslan Bilovol (rbilovol) <[email protected]> Subject: RE: [OE-core] [PATCH] systemd: move systemctl utility to separate subpackage Additionally, changing the packaging does not affect what is added to the sysroot. //Peter > -----Original Message----- > From: [email protected] <openembedded- > [email protected]> On Behalf Of Alexander Kanavin via > lists.openembedded.org > Sent: den 10 februari 2025 18:20 > To: [email protected] > Cc: Ross Burton <[email protected]>; openembedded- > [email protected]; Ruslan Bilovol (rbilovol) > <[email protected]> > Subject: Re: [OE-core] [PATCH] systemd: move systemctl utility to separate > subpackage > > They're not actually copied. They're hard-linked from > sysroots-components/. This is a cheap operation and it doesn't waste > disk space. > > Alex > > On Mon, 10 Feb 2025 at 18:05, Oleksiy Obitotskyy via > lists.openembedded.org <[email protected]> > wrote: > > > > Hi Alexander, > > > > By 'deploying whole systemd' I mean next: > > > > Every component copy and installs packages with libraries, utilities and > config files in component local sysroot, i.e. directory used to create > final component image: > > > > libsystemd0_255.4 > > libsystemd-shared_255.4 > > systemd_255.4 > > > > So, on disk we have duplication of files for every component that depend > on the systemctl. > > In case of separate subpackage we have one root component depend on the > systemd and all other components will contain only systemd-systemctl > package content. > > > > Of course, I understand it's quite a specific scenario. > > > > Regards, > > Oleksiy > > > > ________________________________ > > From: Alexander Kanavin <[email protected]> > > Sent: Monday, February 10, 2025 13:03 > > To: Oleksiy Obitotskyy -X (oobitots - GLOBALLOGIC INC at Cisco) > <[email protected]> > > Cc: Ross Burton <[email protected]>; openembedded- > [email protected] <[email protected]>; > Ruslan Bilovol (rbilovol) <[email protected]> > > Subject: Re: [OE-core] [PATCH] systemd: move systemctl utility to > separate subpackage > > > > On Mon, 10 Feb 2025 at 13:01, Oleksiy Obitotskyy via > > lists.openembedded.org <[email protected]> > > wrote: > > > We have next situation: > > > - a lot of software components that depend on packages and deploy all > packages they depend on locally inside component. > > > - some components directly depend on systemctl only (e.g. this binary > used in scripts), so for every component we have to deploy whole systemd > locally. > > > - finally, all/some of those components will be merged in some way and > will use systemd/libsystemd, but until then it will be nice to get rid of > such duplication. > > > > I'm sorry, but this does not quite make sense. You need to more > > specifically describe what 'deploying whole systemd' means, and why is > > that problematic. > > > > Alex > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#211160): https://lists.openembedded.org/g/openembedded-core/message/211160 Mute This Topic: https://lists.openembedded.org/mt/111032725/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
