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

["Bezdeka, Florian" <florian.bezdeka@siemens.com>]

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.

Best regards,
Florian

> 
> Best regards, R-