-----BEGIN PGP SIGNED MESSAGE-----
On Monday 13 June 2011, Jeff Johnson <firstname.lastname@example.org> wrote:
> On Jun 13, 2011, at 11:05 AM, Eric MSP Veith wrote:
> > What's the preferred way to initially populate a chroot?
> The only difference in rpm-5.3 related ro your issue
> is running dbconvert.sh in %posttrans.
I wasn't refering to rpm5/dbconvert.sh in that paragraph of mine, but
considering that I chose a wrong approach in the past with populating
chroots _in general_. Sorry if I didn't express myself clearly. I do not
trust dbconvert.sh to automagically find out whether a RPMDB needs
converting or not, hence I do not call it from rpm's %post.
What I wanted to ask was: Considering installing RPM packages into a system
initially, such as it often happens when creating a build chroot, what's the
best approach one can choose here?
> Everything is _EXACTLY_ as has always been implemented with
> rpm and chroot(2). There are no changes:
> A script/executable invoked while installing with rpm -r
> can escape a chroot and do whatever it wishes.
Sure, in that case I gladly eat my hat or do something similar as to punish
myself for my own stupidity since I'm the one creating %post & co. :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
Received on Mon Jun 13 17:29:10 2011