On Tue, Oct 24, 2017 at 11:49 AM, Helmut Grohne <hel...@subdivi.de> wrote: > I've been bitten by pregenerated files more than once and dislike your > sketched solution. At the same time I acknowledge that it may be > unavoidable. [...]
I see what you mean: The choice would be whether or not to add code to error out if the pregenerated files don't match what was actually generated. If you don't, you risk people forgetting to update the files and therefore having the bootstrap build be broken. If you do, then you risk the normal package build breaking unnecessarily because of some change in a newer version of yui-compressor or ruby-compass / sass. > The other major alternative is moving doxygen to Build-Depends-Indep and > thus move the generated documentation to arch:all packages. This makes > more sense conceptually as it would remove doxygen from the bootstrap > set entirely, but results in more work and more binary packages. I agree that would be the optimal solution. Practically, though, as you already hinted, I think there are probably enough packages in the core bootstrap set that would need to be updated, that it might take a while and having some interim measure in the meantime would be good. (And if eventually we want Architecture: all packages also to be bootstrappable from a minimal starting set, then there would be some cases also requiring a "nodocs" build profile, so for example you could build libasound2-data or libthai-data without needing to build libasound2-doc or libthai-doc. And this point would also be the biggest issue I would have with the solution of moving the JS stuff into separate files and a separate package: you would still need to bootstrap the JS files somehow in this scenario, until all the source packages that need to would provide a bootstrap build without doxygen docs.) -- Daniel
