All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Beckerus <hans.beckerus@gmail.com>
To: Jochen Trumpf <Jochen.Trumpf@anu.edu.au>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: remove /usr/share/terminfo
Date: Sun, 24 Mar 2013 15:01:03 +0100	[thread overview]
Message-ID: <514F071F.6090507@gmail.com> (raw)
In-Reply-To: <6119177.GIhaGmj4Be@jake>

On 2013-03-24 11:06, Jochen Trumpf wrote:
> Hi Hans,
>
> I am not subscribed to [yocto], just browsing it occasionally, so please
> excuse the private email.
>
> For this sort of thing I am using the following in my image recipe (stolen
> from some gumstix image recipe in meta-gumstix-extras, danny branch):
>
> -- cut --
> # this section removes remnants of legacy sysvinit support
> # for packages installed above
> IMAGE_FILE_BLACKLIST += " \
>                          /etc/init.d/crond \
>                          /etc/init.d/dbus-1 \
>                          /etc/init.d/sshd \
>   "
>
> remove_blacklist_files() {
>          for i in ${IMAGE_FILE_BLACKLIST}; do
>                  rm -rf ${IMAGE_ROOTFS}$i
>          done
>
> }
>
> ROOTFS_POSTPROCESS_COMMAND =+ "remove_blacklist_files ; "
> -- cut --
>
> You can add arbitrary commands to ROOTFS_POSTPROCESS_COMMAND, e.g. your link
> to the network share. As you can see, you can use wildcards in the blacklist
> entries, or anything that rm -rf will understand.
>
> In case you want to use a similar mechanism to ADD files that are not already
> present on your build machine, that is not (easily) possible since
> image.bbclass does not support do_fetch, so SRC_URI does not work within an
> image recipe. The philosophy seems to be that you need a separate recipe to
> add things.
>
> Hope this helps.
>
> Cheers,
> Jochen
>
> P.S.: Feel free to forward this to the list if you think it might be
> interesting for other people.

Hi Jochen. Thanks for the information. As you might have seen already, I 
solved it by using a .bbappend for ncurses, but I must admit that your 
solution is a lot more elegant. I will try your approach instead and 
keep it in mind when needing something similar in the future.

Hans



       reply	other threads:[~2013-03-24 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6119177.GIhaGmj4Be@jake>
2013-03-24 14:01 ` Hans Beckerus [this message]
2013-03-18 12:13 remove /usr/share/terminfo Hans Beckérus
2013-03-19  9:34 ` Hans Beckérus

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=514F071F.6090507@gmail.com \
    --to=hans.beckerus@gmail.com \
    --cc=Jochen.Trumpf@anu.edu.au \
    --cc=yocto@yoctoproject.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.