From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>,
"Shakeel, Muhammad" <muhammad_shakeel@mentor.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] update-rc.d: Remove init.d dir if sysvinit is not in distro features
Date: Fri, 19 Jul 2013 16:13:15 +0100 [thread overview]
Message-ID: <76349842.krt1SjzMLB@helios> (raw)
In-Reply-To: <CABcZAN=z2JMb9XzkCfwFSYwezY7otMGxbYfQr_RboUxkSHcNPg@mail.gmail.com>
On Friday 19 July 2013 08:02:32 Chris Larson wrote:
> On Fri, Jul 19, 2013 at 4:53 AM, Shakeel, Muhammad
> <muhammad_shakeel@mentor.com> wrote:
> > From: Muhammad Shakeel <muhammad_shakeel@mentor.com>
> >
> > If sysvinit is not supported DISTRO_FEATURE than there is no need to
> > package related initialization scripts.
> >
> > Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com>
>
> If we stop shipping init.d for non-sysvinit distros, which makes sense, we
> should also consider automatically enabling/disabling sysv compat support
> in the systems build based on that distro feature also. So, I support this
> commit, but am proposing adding another for consistency :)
Yes, actually at the moment I think we cannot delete the sysvinit initscripts
unless the recipe also inherits systemd, otherwise there will be no fallback
to sysvinit compatibility and the daemon will no longer be started.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-19 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 11:53 [PATCH 1/2] systemd: Remove systemd_unitdir if systemd is not in distro features Shakeel, Muhammad
2013-07-19 11:53 ` [PATCH 2/2] update-rc.d: Remove init.d dir if sysvinit " Shakeel, Muhammad
2013-07-19 15:02 ` Chris Larson
2013-07-19 15:13 ` Paul Eggleton [this message]
2013-07-23 13:59 ` [PATCH 1/2] systemd: Remove systemd_unitdir if systemd " Burton, Ross
2013-07-24 6:57 ` Muhammad Shakeel
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=76349842.krt1SjzMLB@helios \
--to=paul.eggleton@linux.intel.com \
--cc=clarson@kergoth.com \
--cc=muhammad_shakeel@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
/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