On Thu, 2012-06-28 at 14:28 -0400, Mike Miller wrote:
> On Thu, Jun 28, 2012 at 11:30 AM, James Antill wrote:
> > Not sure how this can work well with --installroot, also don't see how
> > it could have worked in 3.2.25.
>
> Works well enough for me with --installroot. The host's value of
> %_dbpath is now used consistently by rpm and yum. The rpmdb is
> created/updated inside installroot under this directory. Packages are
> unpacked into installroot. Subsequent rpm/yum commands with the same
> installroot access the rpmdb at the correct path.
>
> Chroot into the installroot, yeah you may have some minor
> configuration issues to work out, but ATM I am only looking at
> installing/updating the chroot from the host.
>
> If you can suggest specific things that may break I'm willing to test them
> out.
Right, what I meant is that the value of %_dbpath outside a chroot is
not necessarily the same as the value inside the chroot. So
"chroot /blah yum" and "yum --installed=/blah" aren't going to do the
same things.
But I just checked and rpm.TransactionSet("/tmp/foo") doesn't use any
of the macro data inside the chroot (I assumed it would) ... so this
patch makes yum consistent.
Sorry, for the noise.
> In 3.2.25 yum only accessed rpmdb through the rpm module, which
> consistently uses %_dbpath.
Ahh. That makes sense.
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
