On 01/18/2016 10:44 PM, Burton, Ross wrote:
On 13 January 2016 at 03:23, Chen Qi <qi.c...@windriver.com
<mailto:qi.c...@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
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
