> Indeed, what we want here basically is to allow the user to swap out the
> respective build script as defined in the spec with their own shell (script)
> that executes in the exact same environment, thus giving them access to all
> of its internals for their own purposes, including just `echo`ing the env
> vars.
Correction: We don't want them to *replace* the script of course, just *extend*
it (as you noted).
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3147#issuecomment-2154288844
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3147/2154288...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
