Hmh, i've read some trough the code right away. As it seems, the log function is just called once per package upgraded, so my intention is rather to look at the list and deplist building and execution of the update. I'm not very happy reading trough the code, i don't really get warm with it as fast as i want, maybe caused by the fact i havn't been developing in c for the past 2 years, as well as i developed in c++, not pure c. Though, i'm trying to understand the architecture behind dep building. Seems not "my way" as often in os applications, but it seems to work. What i'm wondering is why sync is that often needed (see the log), especially in a linear operation without threads. Last but not least, i've taken a look into package signing, missing some documentation on this tough (gnupg made easy). Merry christmas, // STi On Sunday 24 December 2006 23:32, Dan McGee wrote:
Just thought I'd send this email before I forgot about it. Here is a log from my pacman3 -Syu yesterday:
http://pastebin.archlinux.org/548
The aspell upgrade alone was logged 9 times...so I'm thinking there is a bit of an issue here with the way log entries are being written to the file. I haven't looked at the logging code enough yet to know what is going on, but I thought I'd at least present a concrete example to the list.
Happy holidays to everyone!
-Dan
_______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://www.archlinux.org/mailman/listinfo/pacman-dev