Re: macro(s) to use in RPM spec for /usr/lib/modules-load.d
On Sat, May 19, 2018 at 05:55:16PM +0100, Sérgio Basto wrote: > On Sat, 2018-05-19 at 15:08 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Sat, May 19, 2018 at 02:38:13PM +0100, Sérgio Basto wrote: > > > On Fri, 2018-05-18 at 17:54 -0500, Jason L Tibbitts III wrote: > > > > > > > > > "ES" == Eric Smith writes: > > > > > > > > ES> What macro(s) should I use in an RPM spec to refer to a > > > > directory > > > > ES> like /usr/lib/modules-load.d, which is under /usr/lib even if > > > > libdir > > > > ES> is /usr/lib64? Is there something better than > > > > ES> %{_usr}/lib/modules-load.d? > > > > > > > > It seems that there isn't. I would just use /usr/lib/modules- > > > > load.d > > > > directly. > > > > > > > > You will get an rpmlint complaint about direct use of /usr/lib, I > > > > suppose. Not much to be done about that. Technically a macro > > > > for > > > > this > > > > could be added, but only a few packages need to do this so I > > > > suspect > > > > it > > > > wouldn't be worth it. > > > > > > from VirtualBox.spec we use : > > > > > > %{_prefix}/lib/modules-load.d/ > > > > https://github.com/systemd/systemd/pull/9036 > > Quote: > " > %_environmnentdir /usr/lib/environment.d > %_modulesloaddir /usr/lib/modules-load.d > %_modprobedir /usr/lib/modprobe.d > > This makes installing files there more convenient because people don't > need to construct the path from %_prefix/lib/… . > > See https://lists.fedoraproject.org/archives/list/devel@lists.fedorapro > ject.org/thread/GBF5WJLTQVSXMHGYGBF3723ZYCWFBR7C/. > " > > hum , when this systemd will be availble on Fedora 28 ? "this systemd" == "systemd 239", not released yet. Generally, we don't upgrade systemd in a given Fedora release, because of concerns about backward compatibility. But this is trivial to backport, so we certainly could add it in F28 or even F27. > BTW about loadmodules [1], fedora-loadmodules.service is in initscripts > package[2] and have some files related files [3] but is not used by > any package [4] , this is really necessary ? have this second location. > Shouldn't fedora-loadmodules.service be remove from initscripts ? fedora-loadmodules.service is about /etc/sysconfig/modules/*.modules and /etc/rc.modules, which are scripts that are executed by this service. modules-load.d is a bunch of declarative files that list modules to load. The initscripts maintainer is planning to deprecate some parts, including fedora-loadmodules.service, but this has no bearing really on this PR. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LCXHYBIQO55ZX5TBF3P2PPSLO66NSM6J/
Re: macro(s) to use in RPM spec for /usr/lib/modules-load.d
On Sat, 2018-05-19 at 15:08 +, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, May 19, 2018 at 02:38:13PM +0100, Sérgio Basto wrote: > > On Fri, 2018-05-18 at 17:54 -0500, Jason L Tibbitts III wrote: > > > > > > > > "ES" == Eric Smith writes: > > > > > > ES> What macro(s) should I use in an RPM spec to refer to a > > > directory > > > ES> like /usr/lib/modules-load.d, which is under /usr/lib even if > > > libdir > > > ES> is /usr/lib64? Is there something better than > > > ES> %{_usr}/lib/modules-load.d? > > > > > > It seems that there isn't. I would just use /usr/lib/modules- > > > load.d > > > directly. > > > > > > You will get an rpmlint complaint about direct use of /usr/lib, I > > > suppose. Not much to be done about that. Technically a macro > > > for > > > this > > > could be added, but only a few packages need to do this so I > > > suspect > > > it > > > wouldn't be worth it. > > > > from VirtualBox.spec we use : > > > > %{_prefix}/lib/modules-load.d/ > > https://github.com/systemd/systemd/pull/9036 Quote: " %_environmnentdir /usr/lib/environment.d %_modulesloaddir /usr/lib/modules-load.d %_modprobedir /usr/lib/modprobe.d This makes installing files there more convenient because people don't need to construct the path from %_prefix/lib/… . See https://lists.fedoraproject.org/archives/list/devel@lists.fedorapro ject.org/thread/GBF5WJLTQVSXMHGYGBF3723ZYCWFBR7C/. " hum , when this systemd will be availble on Fedora 28 ? BTW about loadmodules [1], fedora-loadmodules.service is in initscripts package[2] and have some files related files [3] but is not used by any package [4] , this is really necessary ? have this second location. Shouldn't fedora-loadmodules.service be remove from initscripts ? Thanks, [1] systemctl list-unit-files | grep modules fedora-loadmodules.service static systemd-modules-load.servicestatic [2] rpm -qf /usr/lib/systemd/system/fedora-loadmodules.service -i [3] rpm -qf /usr/lib/systemd/system/fedora-loadmodules.service -l | grep modules /etc/sysconfig/modules /usr/lib/systemd/fedora-loadmodules /usr/lib/systemd/system/basic.target.wants/fedora-loadmodules.service /usr/lib/systemd/system/fedora-loadmodules.service [4] dnf repoquery -f "/usr/lib/systemd/fedora-loadmodules/*" -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/HHSKQIZNJJ4AAQKTUYIOQN32KBL53TDC/
Re: macro(s) to use in RPM spec for /usr/lib/modules-load.d
On Sat, May 19, 2018 at 02:38:13PM +0100, Sérgio Basto wrote: > On Fri, 2018-05-18 at 17:54 -0500, Jason L Tibbitts III wrote: > > > > > > > "ES" == Eric Smith writes: > > > > ES> What macro(s) should I use in an RPM spec to refer to a directory > > ES> like /usr/lib/modules-load.d, which is under /usr/lib even if > > libdir > > ES> is /usr/lib64? Is there something better than > > ES> %{_usr}/lib/modules-load.d? > > > > It seems that there isn't. I would just use /usr/lib/modules-load.d > > directly. > > > > You will get an rpmlint complaint about direct use of /usr/lib, I > > suppose. Not much to be done about that. Technically a macro for > > this > > could be added, but only a few packages need to do this so I suspect > > it > > wouldn't be worth it. > > from VirtualBox.spec we use : > > %{_prefix}/lib/modules-load.d/ https://github.com/systemd/systemd/pull/9036 Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LH273KKFRSSDZECHV6HWMXZNZOVOVGUI/
Re: macro(s) to use in RPM spec for /usr/lib/modules-load.d
On Fri, 2018-05-18 at 17:54 -0500, Jason L Tibbitts III wrote: > > > > > > "ES" == Eric Smith writes: > > ES> What macro(s) should I use in an RPM spec to refer to a directory > ES> like /usr/lib/modules-load.d, which is under /usr/lib even if > libdir > ES> is /usr/lib64? Is there something better than > ES> %{_usr}/lib/modules-load.d? > > It seems that there isn't. I would just use /usr/lib/modules-load.d > directly. > > You will get an rpmlint complaint about direct use of /usr/lib, I > suppose. Not much to be done about that. Technically a macro for > this > could be added, but only a few packages need to do this so I suspect > it > wouldn't be worth it. from VirtualBox.spec we use : %{_prefix}/lib/modules-load.d/ > - J< > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelin > es > List Archives: https://lists.fedoraproject.org/archives/list/devel@li > sts.fedoraproject.org/message/3YWZ3VR2QNRHCJK3K2JLTE7453UAL47C/ -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LHN3D3HVD2WAE3S4IBYQXOPHGFCNRF6W/
Re: macro(s) to use in RPM spec for /usr/lib/modules-load.d
> "ES" == Eric Smith writes: ES> What macro(s) should I use in an RPM spec to refer to a directory ES> like /usr/lib/modules-load.d, which is under /usr/lib even if libdir ES> is /usr/lib64? Is there something better than ES> %{_usr}/lib/modules-load.d? It seems that there isn't. I would just use /usr/lib/modules-load.d directly. You will get an rpmlint complaint about direct use of /usr/lib, I suppose. Not much to be done about that. Technically a macro for this could be added, but only a few packages need to do this so I suspect it wouldn't be worth it. - J< ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/3YWZ3VR2QNRHCJK3K2JLTE7453UAL47C/
macro(s) to use in RPM spec for /usr/lib/modules-load.d
What macro(s) should I use in an RPM spec to refer to a directory like /usr/lib/modules-load.d, which is under /usr/lib even if libdir is /usr/lib64? Is there something better than %{_usr}/lib/modules-load.d? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/GBF5WJLTQVSXMHGYGBF3723ZYCWFBR7C/