how to remove all traces of a previous package build?

how to remove all traces of a previous package build?

[Robert P. J. Day]

  surely a dumb question, but what's the recipe for deleting every
trace of a single previous package build, so i know i'm rebuilding it
absolutely from step one?  i'll use that to test a rebuild of the
packages that are failing for me.

rday
--


========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

Re: how to remove all traces of a previous package build?

[Richard Purdie]

On Fri, 2009-11-13 at 05:56 -0500, Robert P. J. Day wrote:
> surely a dumb question, but what's the recipe for deleting every
> trace of a single previous package build, so i know i'm rebuilding it
> absolutely from step one?  i'll use that to test a rebuild of the
> packages that are failing for me.

bitbake X -c clean

where X is the package you want to remove.

Cheers,

Richard

Re: how to remove all traces of a previous package build?

[Eric Bénard]

Hi Robert,

Robert P. J. Day a écrit :
>   surely a dumb question, but what's the recipe for deleting every
> trace of a single previous package build, so i know i'm rebuilding it
> absolutely from step one?  i'll use that to test a rebuild of the
> packages that are failing for me.
> 
I think bitbake -c clean package does what you want.

Eric

Re: how to remove all traces of a previous package build?

[Michael Smith]

On Fri, 13 Nov 2009, Richard Purdie wrote:

> On Fri, 2009-11-13 at 05:56 -0500, Robert P. J. Day wrote:
> > surely a dumb question, but what's the recipe for deleting every
> > trace of a single previous package build, so i know i'm rebuilding it
> > absolutely from step one?  i'll use that to test a rebuild of the
> > packages that are failing for me.
> 
> bitbake X -c clean

Then remove all packages under tmp/deploy; also tmp/pkgdata/*/X and
tmp/pkgdata/*/runtime/X*; and tmp/staging/*/*/shlibs/X*. Otherwise you may 
get problems if you've switched PACKAGE_ARCH in a recipe, or switched 
between packages that provide the same shared library.

I don't think there's a way to remove files from the staging directory. 
Maybe with packaged staging?

Mike

Re: how to remove all traces of a previous package build?

[Przemyslaw Wesolek]

Eric Bénard wrote:
> Hi Robert,
> 
> Robert P. J. Day a écrit :
>>   surely a dumb question, but what's the recipe for deleting every
>> trace of a single previous package build, so i know i'm rebuilding it
>> absolutely from step one?  i'll use that to test a rebuild of the
>> packages that are failing for me.
>>
> I think bitbake -c clean package does what you want.

Or '-c distclean' if you also want to remove source. :)

Przemek

Re: how to remove all traces of a previous package build?

[Chris Conroy]

On Fri, 2009-11-13 at 07:00 -0500, Michael Smith wrote:
> On Fri, 13 Nov 2009, Richard Purdie wrote:
> 
> > On Fri, 2009-11-13 at 05:56 -0500, Robert P. J. Day wrote:
> > > surely a dumb question, but what's the recipe for deleting every
> > > trace of a single previous package build, so i know i'm rebuilding it
> > > absolutely from step one?  i'll use that to test a rebuild of the
> > > packages that are failing for me.
> > 
> > bitbake X -c clean
> 
> Then remove all packages under tmp/deploy; also tmp/pkgdata/*/X and
> tmp/pkgdata/*/runtime/X*; and tmp/staging/*/*/shlibs/X*. Otherwise you may 
> get problems if you've switched PACKAGE_ARCH in a recipe, or switched 
> between packages that provide the same shared library.
> 
> I don't think there's a way to remove files from the staging directory. 
> Maybe with packaged staging?
> 
> Mike


I almost wonder if we should consider adding a task which handles the
above in addition to the standard bitbake clean. I was burned a few
weeks ago by having a stale package in my deploy directory that kept
getting chosen over the new one I was building due to some versioning
nastiness. I can see how automatically purging stuff from deploy would
be considered destructive, but IMHO there should be a command which just
nukes every last bit of a package the build system knows about.

--Chris