[
https://issues.apache.org/jira/browse/BIGTOP-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078314#comment-14078314
]
Sean Mackrory commented on BIGTOP-116:
--------------------------------------
IMO, we should decide at build-time whether the particular distros packages
should use SysV init scripts or systemd. I wouldn't see that as something
passed in by Make or Gradle, but a conditional that we trigger on in the spec
file (search for the suse_version and mgaversion macros - they're used a lot)
or rules file (I'm not so sure we've done this yet - but I believe packages
should usually be built on the same distribution as what you're targeting, so
perhaps we can use lsb_release, etc. in rules files?).
This has the potential to be rather messy, since you're replacing which file
gets included in the package and we'll have a bunch if if / else's everywhere,
so we should look for some nice clean way to express that logic consistently
across all services. Does systemd still use chkconfig for enabling / disabling
services? Because if it doesn't, we also need to swap postinst and prerm
scriptlets...
> Add support for systemd
> -----------------------
>
> Key: BIGTOP-116
> URL: https://issues.apache.org/jira/browse/BIGTOP-116
> Project: Bigtop
> Issue Type: New Feature
> Components: General
> Affects Versions: 0.3.0
> Reporter: Peter Linnell
> Assignee: Peter Linnell
>
> We need to plan for adding native systemd support. Future Fedora and openSUSE
> versions will have this installed as default on a new install. Upgrading from
> 11.4 > 12.1 will retain sysv. Looking at what has happened in openSUSE 12.1
> development will help a lot to guide adding the new bits.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
