Arnaud Quette
2012-Apr-10 20:52 UTC
[Nut-upsdev] Fix broken systemd integration in the build system
Hi Michal, I'm finally back on systemd integration with NUT. I've cc'ed Stanislav, since I've heard Suse is moving to systemd too. I've been investigation on your systemd integration in the tree, found a strange integration and understood why. I've fixed this with 2 commits: - r3528: only generate .in from configure, thus removing this annoying autoreconf msg - r3529: which you will want to revert for now, since it removes the hardcoded paths... see below. so all this lead my again to an incomplete effort on my side: the NUT Packaging Standard. here, upsd and upsmon are installed in /usr/bin, while upsdrvctl and drivers are in /sbin. thus you can't use configure pattern substitution (@SBINDIR@) to remove hard coded paths in template files. so for now, once 2.6.4 is out, just revert r3529. I'll then relaunch this NPS effort, for 2.8 series, and we'll have rooms to discuss all these packaging things. on a separate topic, we will also (Stan, you and I) have to discuss systemd and halt hook. You (Michal) may want to revive the thread you told me, including -upsdev list this time. I'll moderate cross msg on the nut side... cheers, Arnaud -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20120410/248f20ec/attachment.html>
Michal Hlavinka
2012-Apr-11 13:51 UTC
[Nut-upsdev] Fix broken systemd integration in the build system
On 04/10/2012 10:52 PM, Arnaud Quette wrote:> Hi Michal, > > I'm finally back on systemd integration with NUT. > I've cc'ed Stanislav, since I've heard Suse is moving to systemd too. > > I've been investigation on your systemd integration in the tree, found a > strange integration and understood why. > I've fixed this with 2 commits: > - r3528: only generate .in from configure, thus removing this annoying > autoreconf msg > - r3529: which you will want to revert for now, since it removes the > hardcoded paths... see below. > > so all this lead my again to an incomplete effort on my side: the NUT > Packaging Standard. > here, upsd and upsmon are installed in /usr/bin, while upsdrvctl and > drivers are in /sbin.This is no longer true for Fedora. Since Fedora 17, there is no /bin nor /sbin now. Everything got moved to /usr/(s)bin. They are symlinks to /usr... for now. http://fedoraproject.org/wiki/Features/UsrMove Don't ask me why they did it, I don't know it either. They tried to explain it in http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge http://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken but I'm not convinced.> thus you can't use configure pattern substitution (@SBINDIR@) to remove > hard coded paths in template files. > > so for now, once 2.6.4 is out, just revert r3529. > I'll then relaunch this NPS effort, for 2.8 series, and we'll have rooms > to discuss all these packaging things. > > on a separate topic, we will also (Stan, you and I) have to discuss > systemd and halt hook.what do you mean exactly?> You (Michal) may want to revive the thread you told me, including > -upsdev list this time.My memory is failing, I don't know what thread you mean? Cheers Michal
Stuart D Gathman
2012-Apr-11 14:29 UTC
[Nut-upsdev] Fix broken systemd integration in the build system
Long ago, Nostradamus foresaw that on Apr 11, Michal Hlavinka would write:> This is no longer true for Fedora. Since Fedora 17, there is no /bin nor > /sbin now. Everything got moved to /usr/(s)bin. They are symlinks to /usr... > for now.In the /sbin world, I have been creating custom nut packages that put all the drivers in /sbin/ups. This reduces changes of name conflicts on a driver, and has less clutter. Other packages use /usr/libexec for plugins and drivers.
Possibly Parallel Threads
- bestfortress driver establishes/loses/establishes communication and so on...
- [PATCH] inspect: improve UsrMove detection (RHBZ#1186935)
- [PATCH] appliance: exclude /usr/lib/firmware
- [PATCH 0/4] p2v: fix virt-p2v-make-disk on Debian
- [PATCH v2] appliance: exclude /lib/firmware