On Jan 3, 2014, at 8:38 AM, bishwajit goswami wrote:
> Hi,
>
> I was checking on a few rpm patches available.
> I found patch as below:
> -#define PLD_CHROOT
> -#ifdef PLD_CHROOT
> - if (rpmdb->db_chrootDone)
> - xx = dbenv->set_data_dir(dbenv, dbhome);
> -#endif
> rpmdb->db_opens++;
>
> I was not able to figure out the context for which this patch was required.
The PLD_CHROOT patch was added more than 6y ago:
http://rpm5.org/community/rpm-cvs/1536.html
It was likely blindly added "just in case" before releasing rpm-5.0 (iirc):
PLD patches are usually correct.
Meanwhile there are *lots* of changes in RPM (and Berkeley DB) since that patch
was added,
I'm not sure any context related to PLD_CHROOT is meaningful.
> Could someone let me know the issue which needed this patch.
You seem to be looking for explanations for why an rpmdb is being accessed
outside of a chroot (as you reported earlier).
However, solaris and a rather old rpm-5.1.x make it difficult to diagnose
from the info you have provided.
73 de Jeff
>
> Thanks and Regards,
> Bishwajit
______________________________________________________________________
RPM Package Manager http://rpm5.org
User Communication List [email protected]
