From: Ross Burton <ross.burton@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] systemd: Add systemd package to PACKAGE var
Date: Tue, 12 Feb 2013 09:08:09 +0000 [thread overview]
Message-ID: <C7C45274F728429FA76E2C1C47BACCDC@intel.com> (raw)
In-Reply-To: <1360657337-7154-1-git-send-email-raj.khem@gmail.com>
On Tuesday, 12 February 2013 at 08:22, Khem Raj wrote:
> If someone defines SYSTEMD_PACKAGES to be different
> then ${PN} then we need to make sure that they get
> added to PACKAGES variable
The only case it won't already be in PACKAGES is if you're creating a package which contains just the service file, which as I've said before isn't recommended - package the service files along with the binaries that they are executing.
Or is there another use-case I'm missing?
Ross
next prev parent reply other threads:[~2013-02-12 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 8:22 [PATCH] systemd: Add systemd package to PACKAGE var Khem Raj
2013-02-12 9:08 ` Ross Burton [this message]
2013-02-12 15:01 ` Anders Darander
2013-02-12 15:06 ` Ross Burton
2013-02-12 16:49 ` Anders Darander
2013-02-12 17:35 ` Khem Raj
2013-02-12 21:06 ` Burton, Ross
2013-02-12 22:42 ` Khem Raj
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=C7C45274F728429FA76E2C1C47BACCDC@intel.com \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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