how best to resolve dependencies
Dan Davis
dansmood at gmail.com
Fri Aug 27 19:10:57 UTC 2010
I use this pure rpm command-line way to check for full package dependency
resolution before burning a DVD:
mkdir /tmp/rpmdb
rpm --initdb --dbpath /tmp/rpmdb
pushd trunk-f13/x86_64/os/Packages
rpm --dbpath /tmp/rpmdb --test -Uvh *.rpm
...
I do the pungi build install steps separately from split media, and after
the build and install:
pungi -c pungi-f13.cfg -G -B -C --name=IE --ver=trunk-f13 --nosource --force
I see that I have some duplicative packages:
[root at FC13BUILD installer]# ls trunk-f13/x86_64/os/Packages/gcc-*
trunk-f13/x86_64/os/Packages/gcc-4.4.4-10.fc13.x86_64.rpm
trunk-f13/x86_64/os/Packages/gcc-4.4.4-2.fc13.x86_64.rpm
trunk-f13/x86_64/os/Packages/gcc-c++-4.4.4-10.fc13.x86_64.rpm
trunk-f13/x86_64/os/Packages/gcc-gfortran-4.4.4-10.fc13.x86_64.rpm
trunk-f13/x86_64/os/Packages/gcc-gfortran-4.4.4-2.fc13.i686.rpm
Is there anyway to prevent that? Is there a better way to check that all
dependencies are resolved based on the manifest?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/kickstart-list/attachments/20100827/3d879412/attachment.htm>
More information about the Kickstart-list
mailing list