Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: meta/lib/oe/rootfs.py: dont' remove any packages by default
Date: Fri, 31 Jul 2015 14:56:15 +0800	[thread overview]
Message-ID: <55BB1C0F.90508@windriver.com> (raw)

Currently, the rootfs.py removes base-passwd, shadow, update-rc.d,
update-alternatives and run-postinsts when package-management not
in IMAGE_FEATURES, this causes two problems:

1) This makes we can't install the removed pkgs to rootfs, such as
    IMAGE_INSTALL_append = " shadow", the shadow can't installed (first
    installed, then removed)

2) The base-passwd has been removed, but the /etc/passwd and /etc/group
    are still existed since they are generated by preinst, this would
    confuse the user, and we can't add a postuninst to remove /etc/passwd
    and /etc/group since they are required when runtime.

I think that we should not remove any pkgs by default, we can add some
interfaces/ways to let the user decide whether to remove them or any
other pkgs, for example, add a REMOVE_PACKAGS variable, leave it as NULL
or only add run-postinsts to it by default.

-- 
Thanks

Robert


             reply	other threads:[~2015-07-31  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  6:56 Robert Yang [this message]
2015-07-31 10:46 ` meta/lib/oe/rootfs.py: dont' remove any packages by default Paul Eggleton
2015-07-31 11:05   ` Jack Mitchell
2015-07-31 11:09   ` Nicolas Dechesne
2015-07-31 11:12     ` Paul Eggleton
2015-07-31 12:01       ` Nicolas Dechesne
2015-08-01  3:57   ` Robert Yang
2015-08-05 10:23     ` Paul Eggleton

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=55BB1C0F.90508@windriver.com \
    --to=liezhi.yang@windriver.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