On Tue, Jul 20, 2010 at 5:32 PM, suvayu ali <span dir="ltr"><<a href="mailto:fatkasuvayu%2Blinux@gmail.com">fatkasuvayu+linux@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 20 July 2010 15:21, Cameron Simpson <<a href="mailto:cs@zip.com.au">cs@zip.com.au</a>> wrote:<br>
> So Adalbert's "rpm -e preload" advice is good advice.<br></div></blockquote><div><br>It's not wrong advice, but it's not "good" advice, either.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">> The package state is kept entirely in the rpm database - it is safe, as<br>
> far as the database integrity goes, to mix use of rpm and yum as suits<br>
> your needs.<br>
><br>
<br>
</div>Please look at my response to Rudolf's post with reasons behind my statement.<br>
</blockquote><div><br>Suvayu is correct. Mixing use of yum and rpm is discouraged for a
reason. If you want to use all the features of yum (at all) then you
should be using yum for everything. The yum database needs to be aware
of every package transaction in order to provide all the value-add it
has to offer. If you're using rpm, you're cutting yum out of the loop
and changing the state of the system outside of yum's ability to record
what you're doing.<br>
<br>Yes, the package state is kept entirely in the rpm database, however, the rpm database does not contain records of transactions performed on that database.<br><br>
To repeat:<br>
<a href="http://illiterat.livejournal.com/7834.html">http://illiterat.livejournal.com/7834.html</a> <br> </div></div>-- <br>Chris<br><br><br><br>