On 02/11/2011 11:49 AM, [email protected] wrote:
Please read an let me know what you think
I like the idea. Reading the questions on the wiki page:
I think the DBus API should be merged into yum. That way it is easier to
make sure the two parts don't get out of sync. But even more important
is that this will tell potential users that the DBus API is a supported
part of yum and they can rely on the ongoing existence and maintenance.
I guess it is easier and faster to develop it in a separate repository,
though. We can review and merge it when it is done. May be we can have
it as a "technology preview" for one release and ask projects to check
if the API is sufficient for their needs (probably by doing an initial
porting effort) and then make the API final in the next release. I think
it would be good to have at least 3 different API users as this is the
minimal number to make sure the API is general enough. I still have to
draw those projects out of my hat, though.
I wonder if the architecture allows running the back end without root
permissions and obtain the privileges to actually change something on
the system later (just before running the transaction) (Sorry, didn't
check out the details, yet).
May be we should also offer a less fine grained progress signal than
RPMProgress. Something that just goes from 0 to 100 to make it easy for
GUI applications to offer just one progress bar for the whole
transaction run as this is a likely use case.
Florian
_______________________________________________
Yum-devel mailing list
[email protected]
http://lists.baseurl.org/mailman/listinfo/yum-devel
