On Thu, 14 Apr 2022 12:15:43 +0200
Vít Ondruch <vondr...@redhat.com> wrote:
>
> Dne 14. 04. 22 v 2:49 Kevin Kofler via devel napsal(a):
> > Germano Massullo wrote:
> >> This problem was caused because I had misinterpreted official Red Hat
> >> configuration [2].
> > The documentation was written with interactive use in mind, not for
> > scripting or packaging. The "scl enable" tool is very impractical for
> > packaging because you would have to prefix it before each and every command.
> > Using bash as the command is a workaround
>
>
> This was always by design. Not sure what else you propose?
>
> BTW the idea was also that there will be more commands such as `enable`,
> so in theory, there could be something like `scl_build` command(script)
> which could get somehow integrated transparently into RPM, but this was
> never done (and unfortunately this design was severely broken in
> scl-utils 2.x :/ ).
>
>
> > that can only possibly work for
> > interactive use. The sourcing trick (that is much more useful for packaging
> > than "scl enable") is unfortunately completely undocumented.
>
>
> The sourcing trick is generally very dangerous. It might be OKish in RPM
> scriptlets, but otherwise it might result in unpredictable behavior of
> the system.
for the record, I took the sourcing trick from chromium
Dan
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
