All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] rootfs: Do not uninstall update-rc.d
Date: Thu, 10 Sep 2015 16:48:41 +0100	[thread overview]
Message-ID: <1441900121.24871.366.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1srrc_mumugSUWW5mhdip5mqK8J_OQkvuzwMY8O1Rjvzmg@mail.gmail.com>

On Tue, 2015-09-08 at 12:38 -0700, Khem Raj wrote:
> On Tue, Sep 8, 2015 at 12:03 AM, Khem Raj <raj.khem@gmail.com> wrote:
> >
> >> On Sep 7, 2015, at 2:48 PM, Phil Blundell <pb@pbcl.net> wrote:
> >>
> >> On Mon, 2015-09-07 at 14:15 -0700, Khem Raj wrote:
> >>>> On Sep 7, 2015, at 12:36 PM, Phil Blundell <pb@pbcl.net> wrote:
> >>>>
> >>>> On Sun, 2015-09-06 at 15:25 +0000, Khem Raj wrote:
> >>>>> update-rc.d is now needed by systemd to interact with sysv
> >>>>> scripts, so if we have a mixed system, then we can not uninstall
> >>>>> update-rc.d as it is going to break systemd functionality
> >>>>
> >>>> The description above implies that you will only uninstall update-rc.d
> >>>> if systemd is present, but that doesn't seem to be what the patch does.
> >>>
> >>> I meant to not say its only for systemd. but that systemd now needs it.
> >>> so update-rc.d is no longer forcefully removed from image depchain.
> >>
> >> Well, right.  But wouldn't it be better only to leave it in there if
> >> it's actually necessary, i.e. if you have systemd and you also have sysv
> >> scripts and the rootfs isn't read-only?  As it stands, your patch will
> >> cause update-rc.d to be left around for people who aren't using systemd,
> >> which seems like a retrograde step.
> >>
> >
> > makes sense. I can improvise on it and check for all constraints in a follow up.
> 
> 
> I have updates this patch in pull branch
> https://github.com/kraj/openembedded-core/commit/c4c574dff9ef689c7694a6055907083e7a018d48

Very good, how am I meant to deal with this though? You never published
a pull url in your original pull request and I can't figure out how to
get a patch file out the github web UI. I guess I can fetch the branch
somewhere, then extract it, but if everyone does this its going to be
rather annoying for me :(.

I really wish people would just post the v2 on the list.

Incidentally, the wrong version of this has gotten merged, I'll likely
revert it then apply this.

Cheers,

Richard



  reply	other threads:[~2015-09-10 15:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 15:25 [PATCH 0/4] Systemd Upgrade Khem Raj
2015-09-06 15:25 ` [PATCH 1/4] busybox: Enable getopt applet Khem Raj
2015-09-06 15:25 ` [PATCH 2/4] rootfs: Do not uninstall update-rc.d Khem Raj
2015-09-07 19:36   ` Phil Blundell
2015-09-07 21:15     ` Khem Raj
2015-09-07 21:48       ` Phil Blundell
2015-09-08  7:03         ` Khem Raj
2015-09-08 19:38           ` Khem Raj
2015-09-10 15:48             ` Richard Purdie [this message]
2015-09-10 23:35               ` Khem Raj
2015-09-10 23:39                 ` Khem Raj
2015-09-06 15:25 ` [PATCH 3/4] systemd: Upgrade 219 -> 225 Khem Raj
2015-09-06 15:25 ` [PATCH 4/4] systemd: Implement OE-Specific systemd-sysv-install Khem Raj
2015-09-07 19:26 ` [PATCH 0/4] Systemd Upgrade Richard Purdie
2015-09-07 20:53   ` Khem Raj
2015-09-07 20:56     ` Richard Purdie
2015-09-07 21:00       ` Khem Raj
2015-09-07 21:09         ` Richard Purdie
2015-09-07 21:12           ` Khem Raj
2015-09-07 21:15             ` Richard Purdie
2015-09-08 10:31             ` Burton, Ross
2015-09-08 18:12               ` Khem Raj
2015-09-08 18:09   ` Khem Raj
2015-09-09 20:13     ` Burton, Ross

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=1441900121.24871.366.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.