Your message dated Tue, 08 Apr 2008 20:51:00 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#380326: debuild: please add ccache support
has caused the Debian Bug report #380326,
regarding [debuild] please add ccache support
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
380326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380326
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: devscripts
Version: 2.9.20
Severity: wishlist
It would be very useful if debuild supported a --ccache parameter to
enable using ccache.
It would just need to add /usr/lib/ccache/ at the beginning of the $PATH.
(This would also add support for distcc, which is usually run by
ccache.)
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 2.10.20
Hi,
On Sun, 2008-03-23 at 19:18 +0000, Adam D. Barratt wrote:
> On Sat, 2006-07-29 at 12:36 +0200, Marco d'Itri wrote:
> > On Jul 29, Marco d'Itri <[EMAIL PROTECTED]> wrote:
> >
> > > It would just need to add /usr/lib/ccache/ at the beginning of the $PATH.
> > And preserve $CCACHE_*.
>
> Although there isn't a dedicated option, it's now possible to achieve
> the desired effect (or will be once 2.10.20 hits the archive, probably
> some time next week).
>
> 2.10.20 will add a --prepend-path option, and --preserve-envvars has
> supported wildcards since 2.10.17, so one could:
>
> debuild --prepend-path=/usr/lib/ccache --preserve-envvars=CCACHE_*
>
> (or the configuration file equivalents).
As 2.10.20 is now in testing, both the options mentioned above are now
available in both sid and lenny. On that basis, I'm marking this bug as
fixed in 2.10.20.
Regards,
Adam
--- End Message ---
