![](https://seccdn.libravatar.org/avatar/1a6c29ce1b0d6ecb5ebe741642119874.jpg?s=120&d=mm&r=g)
Andrei Borzenkov wrote:
On Tue, Apr 26, 2016 at 9:55 AM, Per Jessen <per@computer.org> wrote:
Andrei Borzenkov wrote:
On Tue, Apr 26, 2016 at 9:16 AM, Per Jessen <per@computer.org> wrote:
If anything, systemd-sysv-convert should be invoked automagically, but Package has to call it manually (it is done via macros, but these macros must be explicitly included in spec). And those macros are expanded when package is created, so unless it was built for (open)SUSE and using (open)SUSE macros, this tool won't be called. What happens when it isn't called? I often install the HP Proliant Support Pack which is not specifically openSUSE "compliant", but it works perfectly fine. It has 2-3 init scripts.
It probably simply installs initscript as before without converting it to systemd service. "rpm -q --scripts" is your friend here. Unfortunately the Altair license manager is not available as RPM. The installer is build with InstallAnywhere. The setup file altair_licensing_12.2.0.linux_x64.bin is a shell script with an included binary payload. After executing the shell script a interactive Java/Swing installer starts. Shell scripts can be found in XML files e.g. in InstallScript.iap_xml:
<property name="script"> <string><![CDATA[#!/bin/sh $USER_INSTALL_DIR$/bin/service_helper start]]></string> </property> Debugging this is probably no fun. Greetings, Björn -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org