Follow-up Comment #5, bug #63111 (project make):
>> 2) Keep the change for explicit grouped targets, and revert the change for
pattern rule grouped targets, say that these two will always work
differently.
>
> i suspect, this difference in behavior can cause trouble than the original
bug.
I guess you mean, can cause *more* trouble? In the short term this will be
less trouble, I'm sure, since we aren't changing existing behavior for
(apparently) somewhat used "features". I do agree that going forward it will
be more problematic if they diverge.
>> 3) Keep the change for explicit grouped targets, revert the change for
pattern rule grouped targets...
>
> The same differnce in behavior.
Yes but: the behavior is different than explicit grouped targets _for this
release_ but it's the same as the behavior for pattern rules since forever, so
it's backwards compatible, *and* it gives a warning (but not error) so that
people using build systems that are affected by this can fix their
environments... the goal is that in the next release we'd remove the warning,
install the change of behavior, and re-align the two.
I'm not sure how tricky this idea would be though. Maybe I'll try to code it
and see what it looks like.
> Given that dtc is fixed and the Andreas patches fix coreutils, let us see,
maybe we are good?
We've had 2 projects with issues so far just in the initial testing, which
concerns me given the number of projects out there.
And remember, people upgrade make without necessarily upgrading, or wanting to
upgrade, all their other software. Saying "it's fixed in the latest Git HEAD
for the project" is not necessarily great.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63111>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
