[Yum-devel] Qs regarding YUM code

Creative Innovative innovative_c at yahoo.com
Thu Apr 23 17:16:22 UTC 2009


Thanks James.
 
Actually I have written a YUM plugin, so that after YUM completes RPM Transaction Test, I will be calling an api(similar to ts_all api in rpmtrans.py), that will dump the transaction file, and exits YUM.
 
-SK

--- On Thu, 4/23/09, James Antill <james at fedoraproject.org> wrote:

From: James Antill <james at fedoraproject.org>
Subject: Re: [Yum-devel] Qs regarding YUM code
To: innovative_c at yahoo.com, "yum development" <yum-devel at lists.baseurl.org>
Date: Thursday, April 23, 2009, 1:43 PM

On Wed, 2009-04-22 at 17:36 -0700, Creative Innovative wrote:
>  
> Qs2) Also I noticed that in rpmtrans.py, prior to running transaction,
> the transaction elements, are dumped to a transaction file
> under /var/lib/yum.
> I was exploring this further, to see if I can leverage for one of the
> work projects that I have been looking into. The idea is to write a
> program in C, which takes the latest yum transaction file, parse it
> and for each entry, uses RPM's C apis to add transaction elements, and
> then calls rpmtsRun() to run the transaction.
> Based on preliminary prototyping it seems to work fine.
> If you have any further inputs/suggestions/concerns please let me 
> know.

 Note that in normal usage this file is deleted after the transaction
completes (it's there so that yum-complete-transaction knows what
happened when the transaction fails).

-- 
James Antill <james at fedoraproject.org>
Fedora



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.baseurl.org/pipermail/yum-devel/attachments/20090423/15dd8d33/attachment.htm>


More information about the Yum-devel mailing list