Tim Lauridsen wrote:
seth vidal wrote:
writing a program that downloads pkgs and runs the transaction w/o
duplicating a bunch of code from cli.doTransaction(). this clearly needs
to be fixed.
The standard operating set:
1. download pkgs
2. sig check pkgs
3. test transaction
4. rpm_check_debug transaction
5. ts.check()
6. ts.order()
7. self.runTransaction(cb)
yes, this needs to be much simpler.
-sv
_______________________________________________
Yum-devel mailing list
Yum-devel@linux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
Yes, it sucks, and there is even more step for the time you have
populates self.tsInfo with the actions you want to perform.
1. Solve dependencies.
2. Ask the user for confimation.
3. Download packages.
4. Check signatures.
5 Ask user for gpg key import confimation if needed.
6. Do a test transaction
7. Do the real transaction
But how do we make it better ?.
Add a generic 'processTransaction' to YumBaseCli with some kind of
callback, so it can be extended ??
See the attached pseudo kode.
Tim
------------------------------------------------------------------------
_______________________________________________
Yum-devel mailing list
Yum-devel@linux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
Look like my last post was eaten by the list size limit, so i try again
without attachments.
I have made a prof of concept to how it could work.
Patch to YumBase.
http://timlau.fedorapeople.org/yum/yum-processTransaction.patch
Test Program.
http://timlau.fedorapeople.org/yum/test.py
Tim
_______________________________________________
Yum-devel mailing list
Yum-devel@linux.duke.edu
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
