Description of problem: BZ #1188862 says that scl-utils-2.0 only build new type of collections (collections with env modules). That's why rpmbuild complains about a missing file. It also means that on Fedora I'm not able to build even the simplest meta package that was build-able with older scl-utils. I see that as problem and see the following solution: In case new scl-utils require to create the environment module file, then scl-utils shoould create the minimal environment module automatically. So, what I'm proposing is to add something like this into %scl_install: cat >> %{buildroot}%{_scl_scripts}/%{scl} << EOF #Module1.0 prepend-path X_SCLS %{scl} prepend-path PATH %{_bindir} prepend-path LD_LIBRARY_PATH %{_libdir} prepend-path MANPATH %{_mandir} prepend-path PKG_CONFIG_PATH %{_libdir}/pkgconfig EOF #automaticaly create enable script for compatibility %scl_enable_script If someone would like to re-define it, it's always possible to delete automatically generated file and create own. What is more, I'm not aware of any collection, that would be have problem with those and what is more, I'd add some other variables as well. Even if they are not used, it is imho correct to have them defined all in all collections: # For binaries export PATH="%{_bindir}\${PATH:+:\${PATH}}" # For header files export CPATH="%{_includedir}\${CPATH:+:\${CPATH}}" # For libraries during build export LIBRARY_PATH="%{_libdir}\${LIBRARY_PATH:+:\${LIBRARY_PATH}}" # For libraries during linking export LD_LIBRARY_PATH="%{_libdir}\${LD_LIBRARY_PATH:+:\${LD_LIBRARY_PATH}}" # For man pages; empty field makes man to consider also standard path export MANPATH="%{_mandir}:\${MANPATH}" # For Java Packages Tools to locate java.conf export JAVACONFDIRS="%{_sysconfdir}/java:\${JAVACONFDIRS:-/etc/java}" # For XMvn to locate its configuration file(s) export XDG_CONFIG_DIRS="%{_sysconfdir}/xdg:\${XDG_CONFIG_DIRS:-/etc/xdg}" # For systemtap export XDG_DATA_DIRS="%{_datadir}\${XDG_DATA_DIRS:+:\${XDG_DATA_DIRS}}" # For pkg-config export PKG_CONFIG_PATH="%{_libdir}/pkgconfig\${PKG_CONFIG_PATH:+:\${PKG_CONFIG_PATH}}"
I thinks it make sense to have both "enable" and environment module file generated. Especially this will avoid having all the spec files always running the same copy/pasted commands. Notice in Description #Module1.0 => #%%Module1.0
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Re-opening, since this is still valid request from my PoV.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.