Re: Installer question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Okay, I think I've isolated the problem I was having.  It was in this bit
of 'buildinstall':

UPD_INSTROOT=./upd-instroot
MK_IMAGES=./mk-images

BUILDARCH=`rpm -qp --qf "%{ARCH}" $p/RedHat/RPMS/anaconda-runtime-[0-9]*`

if [ ! -f $UPD_INSTROOT ]; then
    cd $BUILDINSTDIR
    rpm2cpio $p/RedHat/RPMS/anaconda-runtime-[0-9]* | cpio --quiet -iumd
./usr/lib/anaconda-runtime/upd-instroot
usr/lib/anaconda-runtime/upd-instroot
    mv usr/lib/anaconda-runtime/upd-instroot .
    rm -rf usr
else
    cp -a $UPD_INSTROOT $BUILDINSTDIR/upd-instroot
fi
UPD_INSTROOT=$BUILDINSTDIR/upd-instroot

I thought this bit of code checked for the existence of
/usr/lib/anaconda-runtime/upd-instroot and if it existed, it used it. 
Instead it grabs a pristine copy of upd-instroot from the anaconda-runtime
RPM and uses it.  Once I changed UPD_INSTROOT from the above variable to
/usr/lib/anaconda-runtime/upd-instroot, it rebuilt my buildtree with my
updated libraries and executables.  I'm burning the ISO to a CD now to see
if it'll work.  At the very least, it looks promising.

More to come!

-- 
Brian






[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux