All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: can pkg_{pre, post}rm functions be run at all for image creation?
Date: Mon, 4 Aug 2014 09:56:20 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1408040955530.9154@localhost> (raw)
In-Reply-To: <1407160384.6981.57.camel@ted>

On Mon, 4 Aug 2014, Richard Purdie wrote:

> On Mon, 2014-08-04 at 09:42 -0400, Robert P. J. Day wrote:
> >   oooooh ... that's still kind of weaselly terminology. :-) i'm not
> > *trying* to be annoyingly pedantic, but this is just the kind of thing
> > that students tend to ask about, which is why i want to nail the
> > details.
> >
> >   the current docs state that pkg_*rm routines are *not* run during
> > image creation, and i'm going to accept that. that means that if a
> > pkg_*rm routine *is* written with reference to ${D}, as long as that's
> > run on the target, it won't make a difference. so the references to
> > ${D} in that context don't *hurt*, they're just unnecessary. and
> > potentially confusing, which is why i'm trying to clarify this. (every
> > pkg_*rm routine i've seen, *if* it tests the value of ${D}, bailed if
> > it was set, which makes sense if they should never, ever be invoked at
> > image creation time.)
>
> In the interests of being pedantic since I know you value correctness,
> they test $D. If they used ${D}, it would get expanded by bitbake at
> build time which is not what you want.
>
> >   WRT stuff run at rootfs postprocessing time, sure, you could always
> > run a package removal command, but clarify this for me -- once you're
> > into rootfs postprocessing, you're running in a "pseudo" environment
> > such that you are *effectively* running inside that rootfs, no? so in
> > that case, all filename references would be full names WRT to the root
> > filesystem -- no references to ${D}. is that correct? or am i just
> > confused?
>
> Pseudo environment means you can perform operations as root, its not a
> chroot. You could be in a pseudo chroot of course but our image
> generation isn't.

  ok, i think i've got it, thanks, both of you.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



      reply	other threads:[~2014-08-04 13:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-02 16:34 can pkg_{pre, post}rm functions be run at all for image creation? Robert P. J. Day
2014-08-02 19:40 ` Khem Raj
2014-08-02 19:57   ` Robert P. J. Day
2014-08-02 20:09     ` Khem Raj
2014-08-03  6:56       ` Robert P. J. Day
2014-08-04 12:37         ` Paul Eggleton
2014-08-04 13:42           ` Robert P. J. Day
2014-08-04 13:51             ` Paul Eggleton
2014-08-04 13:53             ` Richard Purdie
2014-08-04 13:56               ` Robert P. J. Day [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=alpine.LFD.2.11.1408040955530.9154@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=richard.purdie@linuxfoundation.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 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.