[pacman-dev] release roadmap?

VMiklos vmiklos at frugalware.org
Mon Feb 6 19:55:21 EST 2006


On Mon, Feb 06, 2006 at 11:18:08PM +0100, Aurelien Foret <aurelien at archlinux.org> wrote:
> [10] pacman -Sw
> Outputs are wrong compared to pacman 2.9
> Do not use log callbacks when the -w is used? or filter all outputs in
> trans.c depending on the downloadonly flag?

hmm. what is the problem here?

$ sudo pacman2 -Suw
:: fontconfig-2.3.2-7: ignoring package upgrade (2.3.93-1)
:: wireless_tools: local (28.pre9-1) appears to be newer than repo (frugalware-current/27-6)
:: Above packages will be skipped.  To manually upgrade use 'pacman -S <pkg>'

Targets: bash-completion-20050721-3 bochs-2.2.6-1 fox-1.4.29-2 gaim-1.5.0-4
         gnome-session-2.12.0-3 icewm-1.2.25-1 imlib2-1.2.1-2 intltool-0.34.2-1
         libwnck-2.12.2-2 mdadm-2.3-1 nmap-4.00-1 pacman-tools-0.6.4-1
         pango-1.10.3-1 poppler-0.5.0-3 postfix-2.2.8-2 rrdtool-1.2.12-1

Total Package Size:   16.1 MB

Proceed with download? [Y/n]

:: Retrieving packages from extra-current...
 fox-1.4.29-2-i686        [----------------] 100%    3479K   11225K/s 00:00:00

checking package integrity... done.

$ sudo pacman -Suw
:: Starting local database upgrade...
warning: fontconfig-2.3.2-7: ignoring package upgrade (2.3.93-1)
warning: wireless_tools-28.pre9-1: local version is newer
resolving dependencies... done.
looking for inter-conflicts... done.

Targets: bash-completion-20050721-3 bochs-2.2.6-1 fox-1.4.29-2 gaim-1.5.0-4
         gnome-session-2.12.0-3 icewm-1.2.25-1 imlib2-1.2.1-2 intltool-0.34.2-1
         pango-1.10.3-1 libwnck-2.12.2-2 mdadm-2.3-1 nmap-4.00-1
         pacman-tools-0.6.4-1 poppler-0.5.0-3 postfix-2.2.8-2
rrdtool-1.2.12-1

Total Package Size:   16.1 MB

Proceed with download? [Y/n]


:: Retrieving packages from extra-current...
 fox-1.4.29-2-i686        [----------------] 100%    3479K   13672K/s 00:00:00

checking package integrity... done.

btw it's interesting that the download speed is higher with pacman3 :)

> 
> [11] library symbols naming
> prepends private functions with "_alpm_"
> 
> => it should be done as the last step before a first release to avoid 
> introducing too much changes to the CVS code at once.

hmm. you mean _every_ function that is not declared in alpm.h?

udv / greetings,
VMiklos

-- 
Developer of Frugalware Linux, to make things frugal - http://frugalware.org




More information about the pacman-dev mailing list