On Mon, Mar 03, 2008 at 04:19:11PM +0100, Nagy Gabor wrote:
My opinion: imho between two major libalpm releases we are allowed to tune it [line now ;-] (otherwise we should release only bugfix releases in the future). I may have misinterpreted the reason of revert, but I had "stable API" feeling only (from frugalware). In these situations some kind of pminfo_t-like stuff with alpm_info_get_dl_total() accessors might be a bit more transparent.
I don't know whether the original patch was good or not, but hopefully in the future we will rework the whole transaction system -- so the API as well, if needed.
I have no idea what you are trying to say here. In the same post, you talk about keeping a stable API, and totally reworking the current API. Btw, you did notice this change was on the master branch, which means it will only be part of 3.2, right?