On Thu, 2024-03-14 11:47:13 -0400, Christos Zoulas <christos%zoulas.com@localhost> wrote:
> > ${WORKDIR} is probably a relative path `work', in which case this will
> > copy ${DESTDIR}/libdata/firmware to ${DESTDIR}/work/libdata/firmware,
> > which explains the checkflist errors you saw.
> >
> > Can you try this change instead?
> >
> > -IMAGEPREBUILD=3D ${TOOL_PAX} ${PAX_TIMESTAMP} -rw -pp ${DESTDIR}/libdata/firmware ${WORKDIR}
> > +IMAGEPREBUILD=3D (cd ${DESTDIR} && ${TOOL_PAX} ${PAX_TIMESTAMP} -w libdata/firmware) | (cd ${WORKDIR} && ${TOOL_PAX} -r -pp)
> >
> > (I don't know if there's a way to convince a single pax -rw instance
> > to chdir into a source directory before taking relative paths to be
> > copied into the target.)
>
> Do we have to use pax? why not use tar -C?
I'm actually quite used to use GNU tar, but TBH `pax` is way better
specified. Despite being used to a different archiver, I quite think
that `pax` is the way to go. We'll see where we end with. The hard
part was to track down there that (kernel-embedded) filesystem came
from and why it contained my local build pathes. We'll see where we
end with. The hard part was to track down there that (kernel-embedded)
filesystem came from and why it contained my local build pathes.
MfG, JBG
--
Attachment:
signature.asc
Description: PGP signature