[pacman-dev] pacman -Sw
VMiklos
vmiklos at frugalware.org
Mon Feb 20 19:23:02 EST 2006
On Mon, Feb 20, 2006 at 08:56:40PM +0100, Aurelien Foret <aurelien at archlinux.org> wrote:
> If I look at code more closely at pacman 2.9.8 code, there are several
> chunks of code enclosed by the "if(!downloadonly) { ... }" statement
> which does not exist in the cvs code.
> Basically, in sync_prepare, the "checkconflict" part should not be
> performed.
is it really good? the typical usage of downloadonly is when you have to
update a lot of packages, and you have a fast connection, then later you
can upgrade the packages. in this scenario, imho it's really annoying if
i download a package and later pacman tells me that i can't install the
package i already downloaded
> Idea: when should maybe split the code chunk in sync_prepare dealing
> with deps and conflicts within the "if(!FLAG_NODEPS) { ... }" block in
> two parts:
>
> if(!FLAG_NODEPS) {
> checkdeps...
> }
> if(!FLAG_NOCONFLICT) {
> checkconflict...
> }
>
> with FLAG_NOCONFLICT being a new flag, that the frontend should force
> when running "-Sw" in order to bypass all the conflicts checking.
>
> Thoughts?
or just name it "downloadonly", probably this is the only case the
frontend should use it
udv / greetings,
VMiklos
--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org
More information about the pacman-dev
mailing list