From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail5.wrs.com (mail5.windriver.com [192.103.53.11]) by mail.openembedded.org (Postfix) with ESMTP id 5300A6E687 for ; Fri, 22 Jan 2016 01:38:26 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id u0M1cQeB013215 (version=TLSv1 cipher=AES128-SHA bits=128 verify=OK); Thu, 21 Jan 2016 17:38:26 -0800 Received: from [128.224.162.246] (128.224.162.246) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 21 Jan 2016 17:38:25 -0800 Message-ID: <56A1882A.50802@windriver.com> Date: Fri, 22 Jan 2016 09:38:50 +0800 From: ChenQi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "Burton, Ross" References: <35fd9829f35bd0486288037c7f0a3cf5ada85948.1452655299.git.Qi.Chen@windriver.com> In-Reply-To: X-Originating-IP: [128.224.162.246] Cc: OE-core Subject: Re: [PATCH 1/1] cups: upgrade to 2.1.2 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2016 01:38:29 -0000 Content-Type: multipart/alternative; boundary="------------040401020101020801000608" --------------040401020101020801000608 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit On 01/18/2016 10:44 PM, Burton, Ross wrote: > > On 13 January 2016 at 03:23, Chen Qi > wrote: > > Add PACKAGECONFIG for systemd. And install our own systemd unit files. > > > Why would we want to use our own units over the upstream units? > > Ross Hi Ross, Sorry for the late reply. Our unit files are the same with the Fedora's. And the unit files that cups it self provides have strange names like org.cups.cupsd.socket and org.cups.cupsd.service. And contents are something like below. chenqi@pek-hostel-deb01:~/poky/build-systemd/tmp/work/core2-64-poky-linux/cups/2.1.2-r0/cups-2.1.2/scheduler [1] $ cat org.cups.cupsd.service [Unit] Description=CUPS Scheduler Documentation=man:cupsd(8) [Service] ExecStart=/usr/sbin/cupsd -l Type=simple [Install] Also=org.cups.cupsd.socket org.cups.cupsd.path WantedBy=printer.target So if we use unit files that cups provides, we either change both the file names and the contents, or we use these strange names. Best Regards, Chen Qi --------------040401020101020801000608 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit
On 01/18/2016 10:44 PM, Burton, Ross wrote:

On 13 January 2016 at 03:23, Chen Qi <Qi.Chen@windriver.com> wrote:
Add PACKAGECONFIG for systemd. And install our own systemd unit files.

Why would we want to use our own units over the upstream units?

Ross

Hi Ross,

Sorry for the late reply.

Our unit files are the same with the Fedora's.
And the unit files that cups it self provides have strange names like org.cups.cupsd.socket and org.cups.cupsd.service.
And contents are something like below.

chenqi@pek-hostel-deb01:~/poky/build-systemd/tmp/work/core2-64-poky-linux/cups/2.1.2-r0/cups-2.1.2/scheduler [1] $ cat org.cups.cupsd.service
[Unit]
Description=CUPS Scheduler
Documentation=man:cupsd(8)

[Service]
ExecStart=/usr/sbin/cupsd -l
Type=simple

[Install]
Also=org.cups.cupsd.socket org.cups.cupsd.path
WantedBy=printer.target

So if we use unit files that cups provides, we either change both the file names and the contents, or we use these strange names.

Best Regards,
Chen Qi
--------------040401020101020801000608--