Why not? Changing the inner configure call to
./configure `cat configure.lastrun.build`
Sure, but then there would be a discrepancy with how autogen.lastrun
works. Or should we realize already that autogen.lastrun isn't
actually valued by developers as a "backup copy" of their last
autogen.sh parameters, but it is seen as a precious input file, edited
and certainly not intended to get over-written... and remove the code
to (re)write it from autogen.sh? Anyway, I am not opposed to this
idea. I would perhaps call it configure.args.build (and
configure.args.host, if we remove the "backup copy" aspect)?
--tml
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.