Re: [PATCH 1/1] Reduce disk usage during build by avoiding copies of apt cache

["Roberto A. Foglietta" <roberto.foglietta@gmail.com>]

On Wed, 4 Jan 2023 at 12:00, Bezdeka, Florian
<florian.bezdeka@siemens.com> wrote:
>
> On Wed, 2023-01-04 at 11:26 +0100, Roberto A. Foglietta wrote:
> > On Wed, 4 Jan 2023 at 07:10, Schmidt, Adriaan
> > <adriaan.schmidt@siemens.com> wrote:
> >
> > > > @@ -308,7 +307,8 @@ rootfs_install_sstate_prepare() {
> > > >      # so we use some mount magic to prevent that
> > > >      mkdir -p ${WORKDIR}/mnt/rootfs
> > > >      sudo mount --bind ${WORKDIR}/rootfs ${WORKDIR}/mnt/rootfs -o ro
> > > > -    sudo tar -C ${WORKDIR}/mnt -cpSf rootfs.tar --one-file-system rootfs
> > > > +    lopts="--one-file-system --exclude-caches --exclude=var/cache/apt/archives"
> > >
> > > (several locations):
> > > With the creation of CACHEDIR.TAG, and --exclude-caches, isn't the --exclude=
> > > of that same path redundant?
> >
> > Hi Adriaan,
> >
> > if you look at this, everything has been achieved using exclude option
> >
> >  sudo tar --one-file-system --exclude="var/log/*" \
> > --exclude="var/cache/*" --exclude="var/backups/*" \
> > --exclude="var/tmp/*" --exclude="var/crash/*" \
> > --exclude="var/spool/*" --exclude="var/lib/apt/*" \
> > --exclude-caches --exclude-backups -C ${WORKDIR}/mnt \
> > -cpSf rootfs.tar rootfs
> >
> > however exclude backups and caches are still in place because the user
> > might define further ignoring locations using different ways.
> >
> > P.S.: I have updated and rebased the cherry picking on my 'next'
> > branch and it works pretty well despite is just a subset of all the
> > patches I am experimenting.
>
> Roberto,
>
> nice to see you working on that, but: if you want us to look at
> something (especially on code/patches) please send them - with the
> right version tag - to the list. We can't go and check your repo every
> time and follow all the activity (especially rebasing) that is going on
> there.
>
> Someone already mentioned that: We need to look at patches that are
> based on current Isar next branch. Everything else is basically
> unusable for us.
>

Hi Florian,

I am not going to push my will over you. I like that you will find
your own independent solution whatever the time it takes. After all,
my actual contribution is just for free aka I am just a hobbyist.

The 1st rule of a hobbyist is: if it works on my PC then, it works for
all my world! Sometimes also referred to as Robinson Crusoe 1st rule.
LOL

Just for sake of completeness: the basic-os was built in 8m33s, in the
current 'next' branch it takes 3m6s. It was requiring 43GB of disk
space but now less than 4GB.

The complete build was taking 20m13s but now is around 12m, sometimes
above and sometimes below. It was using 53GB of disk but now it is
just 29GB and I am still working on it to improve it.

Useless is such a big word, after all... ROTFL

Best regards, R-