public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] cups: upgrade to 2.1.2
Date: Fri, 22 Jan 2016 09:38:50 +0800	[thread overview]
Message-ID: <56A1882A.50802@windriver.com> (raw)
In-Reply-To: <CAJTo0LbRy5fd8Wcz5ZqQ0cTjW1o+wJ-m-srL-H0cRknQua9upw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On 01/18/2016 10:44 PM, Burton, Ross wrote:
>
> On 13 January 2016 at 03:23, Chen Qi <Qi.Chen@windriver.com 
> <mailto: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

[-- Attachment #2: Type: text/html, Size: 2601 bytes --]

      reply	other threads:[~2016-01-22  1:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  3:23 [PATCH 0/1] cups: upgrade to 2.1.2 Chen Qi
2016-01-13  3:23 ` [PATCH 1/1] " Chen Qi
2016-01-18 14:44   ` Burton, Ross
2016-01-22  1:38     ` ChenQi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56A1882A.50802@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox