public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] systemd: set default.target to multi-user.target
Date: Mon, 28 Jan 2013 20:48:57 +0100	[thread overview]
Message-ID: <20130128194857.GG16904@jama.palm1.palmone.com> (raw)
In-Reply-To: <CAJTo0LaLw8Z+QizuObvx_GL-dqUe0kSOr2JhQsMmVnj62zG0rw@mail.gmail.com>

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

On Mon, Jan 28, 2013 at 07:27:22PM +0000, Burton, Ross wrote:
> On 28 January 2013 18:27, Martin Jansa <martin.jansa@gmail.com> wrote:
> > So I guess upgrade path from meta-systemd won't be ever provided (e.g.
> > with RPROVIDES/RCONFLICTS/RREPLACES combo).
> 
> I'd prefer not too, but if we have to we can.
> 
> > I wouldn't mind PN-sysvinit, PN-upstart, PN-openrc
> 
> But what's the point when its a distro variable? With systemd daemons
> are actively making code changes instead of it merely being a
> different init file, so an image feature just won't work.

to control which packages should have systemd support just by IMAGE_INSTALL.

With latest systemd.bbclass you can still install them but not enable
them by default, but even after SYSTEMD_AUTO_RRECOMMENDS was introduced
I prefered to turn that off and control what I want in images (or
install from feed).

Imagine situation when someone wants ntpd package just for ocassional
manual sync, but someone else wants to pull ntpd to image together with
systemd .service file to make sure his device is always using right
time.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-01-28 20:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 14:59 [PATCH v2] systemd: set default.target to multi-user.target Radu Moisan
2013-01-25 15:04 ` Burton, Ross
2013-01-25 15:10   ` Richard Purdie
2013-01-28  9:41     ` Radu Moisan
2013-01-25 15:12   ` Martin Jansa
2013-01-25 17:50     ` Burton, Ross
2013-01-25 17:53       ` Andreas Müller
2013-01-25 18:06         ` Martin Jansa
2013-01-25 18:35           ` Andreas Müller
2013-01-25 19:34             ` Martin Jansa
2013-01-25 20:21               ` Ross Burton
2013-01-25 20:26                 ` Martin Jansa
2013-01-25 21:09                   ` Andreas Müller
2013-01-25 23:52                     ` Richard Purdie
2013-01-28 10:44                   ` Burton, Ross
2013-01-28 11:20                     ` Otavio Salvador
2013-01-28 11:48                     ` Andreas Müller
2013-01-28 11:50                       ` Burton, Ross
2013-01-28 18:27                     ` Martin Jansa
2013-01-28 19:27                       ` Burton, Ross
2013-01-28 19:48                         ` Martin Jansa [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=20130128194857.GG16904@jama.palm1.palmone.com \
    --to=martin.jansa@gmail.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