I don't doubt that's what the setup authors intended, but really, it's overly
clever for human beings, that like their commands simple and easy to remember,
it's overly clever for scripts, that like to loop over the same command not
compute complex lists of arguments, it's overly clever for whoever is tasked to
explain it so anyone else, and besides, it does not handle patching of
intermediate sources well.
Which is why from time immemorial, starting with the heroic period when maximum
rpm was written, the documented and actual `%setup` use was not what the setup
authors intended, but one setup call per archive.
So could we make the way people actually use `%setup` work better please?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/551#issuecomment-424052712
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint