Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] skeleton: add systemd network.service unit
Date: Wed, 29 Jan 2014 10:09:34 +0100	[thread overview]
Message-ID: <871tzrxigh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140129082612.GM3867@lukather> (Maxime Ripard's message of "Wed, 29 Jan 2014 09:26:12 +0100")

>>>>> "Maxime" == Maxime Ripard <maxime.ripard@free-electrons.com> writes:

Hi,

 >> Also, as far as I understand, the idea is not to add variables, but
 >> rather to check for the existence of package/foo/*.service and
 >> install that.

 > This also doesn't cover the case anymore where a package would ship
 > together with the source code a systemd unit file. I expect it to be
 > more and more common, and it's something that we will want to use most
 > of the time, and not duplicate the unit file in the buildroot package
 > itself.

Good point. I would certainly not want us to write our own service files
if upstream provides a workable one.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2014-01-29  9:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  1:38 [Buildroot] [PATCH 1/1] skeleton: add systemd network.service unit Ivan Sergeev
2014-01-03 19:13 ` Thomas Petazzoni
2014-01-03 19:41   ` Ivan Sergeev
2014-01-28  1:54     ` [Buildroot] [PATCH 1/1] systemd: add network unit file Ivan Sergeev
2014-06-11 20:34       ` Thomas Petazzoni
2014-06-13 15:42         ` Eric Le Bihan
2014-06-13 15:44           ` Thomas Petazzoni
2014-01-28  7:13     ` [Buildroot] [PATCH 1/1] skeleton: add systemd network.service unit Arnout Vandecappelle
2014-01-28  8:25       ` Maxime Hadjinlian
2014-01-28  8:38         ` Arnout Vandecappelle
2014-01-28 13:20         ` Maxime Ripard
2014-01-28 17:20           ` Arnout Vandecappelle
2014-01-29  8:26             ` Maxime Ripard
2014-01-29  9:07               ` Maxime Hadjinlian
2014-01-29  9:09               ` Peter Korsgaard [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=871tzrxigh.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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