On Tue, 2019-07-09 at 20:19 +0200, Christof Warlich wrote: > Am 09.07.19 um 15:42 schrieb David Boyce: > > I also think the proposal is reasonable but I think it would be > > "stickier", i.e. less likely to get lost, if you filed it as an > > enhancement request via the Savannah bug reporting system. > I'd be glad to do that if it increases the chance to get it in. But > I couldn't find the Savannah bug reporting system (on > https://savannah.gnu.org/). Do I need to create a new user and log in > to be able to file an enhancement request?
https://savannah.gnu.org/bugs/?func=additem&group=make You don't have to make an account in order to file a bug, but be sure to add yourself to mail notifications if you don't create an account, or you won't get any updates. My first reaction is that this solution seems like a very big hammer (in terms of changes to makefile syntax) to handle a relatively rare and specific situation. I wonder if there's an alternative that gives the same result but is a bit less intrusive. What if we do this instead: create a variable which can contain a list of "hidden prerequisites": they will always be built first but they won't cause any changes in the automatic variables. If set globally it will apply to all targets. If set as a target-specific variable then it applies only to that target (and its prerequisites, which can be remediated with the private keyword). This seems like it could be something generally useful, to ensure some targets are always built first, as well as useful in this context. On another topic, note that these changes are of a size that they do meet the requirement for copyright assignment before they can be applied. I can forward you the details if that's something you're interested in. Cheers! _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
