Author: anonym Date: To: The Tails public development discussion list Subject: Re: [Tails-dev] Please review some vagrant optimizations [was:
Shipping a 686-pae kernel]
10/09/12 19:13, intrigeri wrote: > anonym wrote (10 Sep 2012 17:00:55 GMT) :
>> I.e. would you be comfortable with other developers using this
>> option in the fashion I used it previously, as described above?
>
> Fair enough, I could live with that.
Implemented in commit f26b336.
> I think the release process doc should tell very clearly what build
> options should/should not be used at release time, else everyone will
> just fetch the last-used command from their shell history and then
> "it's disabled by default" becomes useless.
Even if you forcibly enable the 'cache' option it be enabled. Building
from stable/testing or a tag will enforce 'cleanall' (commit 38c8394),
which will clear any cache saved to disk before the build. In other
words, you can't shoot yourself in the foot if you follow the current
release process. Hence I'm not sure it's worth documenting this.
