[pacman-dev] [GIT] The official pacman repository branch, master, updated. v3.1.2-75-g73ac9f7
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official pacman repository".
The branch, master has been updated
via 73ac9f7b27c3da538dad0f59c28f67badbb43a64 (commit)
via aecc2fd19037d0580df9600628acace93cb0dd46 (commit)
via 7613f2e21aa4df72e7a520b2cd80c592a0cb63a2 (commit)
via d734ebdde270c1e13e3b910e731bea88d874a51c (commit)
via c2dbbd60bc8a4c90ec32fdbe9098ffae222d00d7 (commit)
via 4fe7eb66eb62ad8537801d8581e472ec594f19f3 (commit)
via 79945ef7ff7787de70aab55e87dca00eb4b87353 (commit)
via d49f42ba752b3ecb3cf02b0b137fc422bfd7c76c (commit)
from d75f693155c3d7e595a779f15beea516d321f228 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 73ac9f7b27c3da538dad0f59c28f67badbb43a64
Merge: d734ebdde270c1e13e3b910e731bea88d874a51c aecc2fd19037d0580df9600628acace93cb0dd46
Author: Dan McGee
commit c2dbbd60bc8a4c90ec32fdbe9098ffae222d00d7 Author: Dan McGee
Date: Tue Jan 22 23:11:31 2008 -0600 Start removing some junk from the function template
I screwed up originally when I accepted the TotalDownload patch, 8ec27835f40e3df1ce409bc3d913587c474a30c3. I didn't realize how deeply it modified libalpm and I probably shouldn't have let it do what it did. This commit reverts much of what that patch added in order to clean up our internal function calls. We can find another way to do it right down the road here but for now it has to go.
Signed-off-by: Dan McGee
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. Bye ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/
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?
participants (3)
-
Dan McGee
-
Nagy Gabor
-
Xavier