pkg_add -u

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

pkg_add -u

fulvio ciriaco-2
Hallo,
I have some ports updated by me,
e.g. emacs-22.1, sawfish-1.3.3 ...
When trying
pkg_add -ui
Candidates for updating sawfish-1.3.3p0 -> sawfish-1.3p9
Candidates for updating auctex-11.14p1 -> auctex-11.14p1
...
auctex installed by me, dependent on emacs-22.1 wants to be
replaced by auctex same version dependent on emacs-21.4,
Does pkg_add -u not check version number?
Fulvio

Reply | Threaded
Open this post in threaded view
|

Re: pkg_add -u

Marc Espie-2
On Fri, Feb 29, 2008 at 10:59:29PM +0100, fulvio ciriaco wrote:

> Hallo,
> I have some ports updated by me,
> e.g. emacs-22.1, sawfish-1.3.3 ...
> When trying
> pkg_add -ui
> Candidates for updating sawfish-1.3.3p0 -> sawfish-1.3p9
> Candidates for updating auctex-11.14p1 -> auctex-11.14p1
> ...
> auctex installed by me, dependent on emacs-22.1 wants to be
> replaced by auctex same version dependent on emacs-21.4,
> Does pkg_add -u not check version number?

No.

Reply | Threaded
Open this post in threaded view
|

Re: pkg_add -u

Ingo Schwarze
In reply to this post by fulvio ciriaco-2
Hi Fulvio,

fulvio ciriaco wrote on Fri, Feb 29, 2008 at 10:59:29PM +0100:

> I have some ports updated by me,
> e.g. emacs-22.1, sawfish-1.3.3 ...
> When trying
> pkg_add -ui
> Candidates for updating sawfish-1.3.3p0 -> sawfish-1.3p9
> Candidates for updating auctex-11.14p1 -> auctex-11.14p1
> ...
> auctex installed by me, dependent on emacs-22.1 wants to be
> replaced by auctex same version dependent on emacs-21.4,
> Does pkg_add -u not check version number?

No, currently, it only compares patch level numbers (not version
numbers) and even that only within the same package repository.

Perhaps setting your PKG_PATH might get part of your job done.
The program pkg_add only considers the packages form the first
repository in the PKG_PATH where it finds at least one matching one.
With the current scheme, considering installed packages as an
additional pseudo-repository is not possible and would not make
any sense: If that pseudo-repository were put at the beginning,
no package would ever get updated, were it put at the end,
it would have no effect whatsoever.

Consider

export PKG_PATH=/usr/ports/packages/386/all/:ftp://openbsd.ftp.fu-berlin.de/snapshots/packages/i386/

or whatever architecture, flavor and mirror you are using.

But if use such settings, do not forget regularly cleaning obsolete
packages out of the directory /usr/ports/packages/386/all/.
With the PKG_PATH shown above, they will always override the public
mirror, even when they become outdated and the mirror has newer ones.

Hope that helps,
  Ingo