[buildd-tools-devel] Bug#810871: Bug#810871: Bug#810871: [sbuild] Please provide a way to set an environment variable to the build directory

[Johannes Schauer]

Hi,

Quoting Katsuhiko Nishimra (2016-01-14 04:53:37)
> On Thu, 14 Jan 2016 00:37:19 +0100 Johannes Schauer <josch at debian.org> wrote:
> > 
> > Is this documentation not working for you:
> > 
> > https://wiki.debian.org/sbuild#Using_.22ccache.22_with_sbuild
> 
> Yes, I've followed the instructions above and encountered cache misses.

I would like to understand why this fails now so I CC-ed Ian Campbell who seems
to be responsible for the last big overhaul of that section in the wiki.

sbuild has been choosing a randomized build path for a long time so I don't
know why it apparently doesn't work anymore all of a sudden.

Maybe something changed in more recent ccache versions?

> > If you just need a stable build path, is the --build-path option not
> > working for you?
> 
> Ah, it's one way.
> I haven't noticed that stable build paths are not a problem even in the
> case where parallel builds are invoked.
> 
> But, if we can specify something like 
>  $build_environment = { 'CCACHE_BASEDIR' => '%BUILD_DIR%'};
> is it more versatile?

Being able to use the percent escapes like this is not supported yet but I can
see how it could be useful to be able to do so. I'll think about it from a more
general perspective.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20160114/55e114df/attachment.sig>