[pacman-dev] [PATCH] New --nonew option (resubmit)

Xavier shiningxc at gmail.com
Sat Mar 1 15:03:39 EST 2008

On Fri, Feb 29, 2008 at 02:11:11PM +0100, Nagy Gabor wrote:
> This is the next member of our target-list filter options (--needed, --unneeded).
> With this option pacman won't add new packages (which cannot be found in localdb), only upgrade/reinstall old ones.
> This implement the request of FS#8137. See also: http://www.archlinux.org/pipermail/pacman-dev/2007-October/009650.html
> I also added sync022.py to test the new option.
> Note: I rephrased the descriptions of --needed to emphasize that it is a filter option (--nonew is usually used with --needed).
> Note: in the future we can implement a new --freshen option == --needed + --nonew.
> +*\--nonew*::
> +	Pacman won't install new (not-yet-installed) packages, except if they are
> +	needed by others (as dependency). This is mostly used in group
> +	operations to restrict pacman to installed packages of the group.
> +	For example 'pacman -S base --nonew --needed' will upgrade your
> +	base group, but won't add new packages from base.
> +	

Should we really support upgrading a particular set of packages (as opposed
to the whole system with -Su) by adding features to ease up that task?

More information about the pacman-dev mailing list