Re: Problem with temporary package build directory removal
fakeroot debian/rules clean works!
Is this standard way of cleaning up the build directories?
On Friday 25 May 2001 13:26, Daniel Stone wrote:
> On Fri, May 25, 2001 at 07:13:14AM -0400, Harry Henry Gebel wrote:
> > On Fri, May 25, 2001 at 12:49:31PM +0200, Alwyn Schoeman wrote:
> > > I'm sorry, I meant dh_clean do not remove this directory. So if
> > > package is foo, then the build process would create debian/foo and
> > > install all the files in that directory tree. Upon dh_clean it should
> > > remove debian/foo, but it doesn't. If it was called debian/tmp it
> > > seems to work, but then I need to add -Pdebian/tmp to most dh_*
> > > commands in debian/rules.
> >
> > Do you have:
> >
> > export DH_COMPAT=3
> >
> > in your rules file? I adopted a package that didn't and found it tried to
> > work in debian/tmp , but when I added the above to the top of my rules
> > file it started using debian/package_name .
>
> You also need to build-depend on debhelper >v3:
> Build-Depends: debhelper (>> 3.0.0)
>
> Because DH_COMPAT=3, makes it use debhelper v3 features.
> Also, the best solution is to put dh_clean as one of the targets for clean:
> in debian/rules. That way, fakeroot debian/rules clean, takes care of it.
>
> My clean: line in debian/rules looks like:
>
> clean:
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
>
> # Clean everything up afterwards.
> -$(MAKE) clean
>
> dh_clean
>
> So, fakeroot debian/rules clean, thoroughly cleans it.
>
> Hope this helps,
>
> :) d
--
~~~~~~~~~~~~~~
Alwyn Schoeman
Prism Wireless
The Internet will destroy the barriers that are isolating people
from decent opportunities based on where they happened to have been born,
and this will be a fundamental transformation of our global society that will
greatly discomfort a lot of worthless people. Then those same worthless people
will create new barriers based on access to source code, licenses,
software permissions, etc. Sigh.
-- Hans Reiser
Reply to: