[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434324#comment-15434324
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9462:
--------------------------------------------

Github user rhtyd commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/1647#discussion_r76004158
  
    --- Diff: debian/rules ---
    @@ -5,8 +5,17 @@ PACKAGE = $(shell dh_listpackages|head -n 1|cut -d '-' -f 
1)
     SYSCONFDIR = "/etc"
     DESTDIR = "debian/tmp"
     
    +ifeq ($(shell lsb_release -sr), 14.04)
    +        SUBSTVARS = -Vjre:Depends="openjdk-7-jre-headless" 
-Vjdk:Depends="openjdk-7-jdk" -Vinit:"Depends:jsvc"
    +else
    +        SUBSTVARS = -Vjre:Depends="openjdk-8-jre-headless" 
-Vjdk:Depends="openjdk-8-jdk" -Vinit:"Depends:systemd"
    --- End diff --
    
    @wido should this be written like:   `-Vinit:Depends="systemd"`. Would it 
be possible to support both systemd/initd environments by adding the dependency 
like `systemd | jsvc` -- this way it would try to install both? On (systemd 
based) Ubuntu 16.04 systemd will be already installed, we can install jsvc for 
all systems -- so why not just depend on jsvc alone? On 14.04, the pkgs can 
continue to use jsvc/initd script and on 16.04 it can uses systemd, both using 
the same packages.
    
    I want us to avoid hosting two separate deb repositories (one for 
non-systemd based and one for systemd based) if possible. Thoughts?


> Systemd packaging for Ubuntu 16.04
> ----------------------------------
>
>                 Key: CLOUDSTACK-9462
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9462
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.10.0, 4.9.1
>
>
> Support for building deb packages that will work on Ubuntu 16.04



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to