mock question how do not clean BUILDROOT after build ?
Sérgio Basto
sergio at serjux.com
Thu Oct 8 00:47:30 UTC 2015
On Seg, 2015-10-05 at 10:07 +0200, Miroslav Suchý wrote:
> Dne 4.10.2015 v 05:22 Sérgio Basto napsal(a):
> > Hi,
> >
> > Mock after building and write the rpms, always execute %clean, doesn't
> > matter if I add --no-cleanup-after, example [1].
> > Have we any simple way to mock not perform %clean, at the end ?
> > I need it to debug the make install ...
> >
> > Thanks,
> >
> > [1]
> > Wrote: /builddir/build/RPMS/libmp4v2-debuginfo-2.1.0-0.4.trunkREV507.fc21.x86_64.rpm
> > Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.ilJSts
> > + umask 022
> > + cd /builddir/build/BUILD
> > + cd mp4v2-trunk
> > + /usr/bin/rm
> > -rf /builddir/build/BUILDROOT/libmp4v2-2.1.0-0.4.trunkREV507.fc21.x86_64
> > + exit 0
> >
>
> --no-cleanup-after tells *mock* to not wipe buildchroot after building.
>
> What you are looking for is to tell *rpmbuild* to not run %clean when building (and then probably tell mock to use
> --no-cleanup-after so you can investigate the artifacts).
>
> So the solution should be:
> mock --rpmbuild-opts=--noclean --no-cleanup-after foo.src.rpm
>
Many thanks it works ! .
But thinking about, shouldn't --no-cleanup-after set rpmbuild with
--noclean ? , I think is what we expect.
--
Sérgio M. B.
More information about the buildsys
mailing list