Subject: Re: User's guide to pkgviews (experimental!)
To: Johnny C. Lam <firstname.lastname@example.org>
From: None <email@example.com>
Date: 01/06/2004 08:35:29
On Mon, Jan 05, 2004 at 11:23:44PM -0800, Johnny C. Lam wrote:
> On Tue, Jan 06, 2004 at 08:11:29AM +0100, Juan RP wrote:
> > On Tue, 6 Jan 2004 06:50:39 +0000
> > "Johnny C. Lam" <jlam@NetBSD.org> wrote:
> > > I've attached a start of a user's guide to using pkgviews for those
> > > users who wish to experiment with the new functionality in pkgsrc.
> > > The following commands will install both pkgsrc/www/lynx and
> > > pkgsrc/www/lynx-current onto the same system using pkgviews:
> > > cd /usr/pkgsrc/www/lynx; make install
> > > cd /usr/pkgsrc/www/lynx-current; make install PKGVIEWS=devel
> > > The stable version of lynx (184.108.40.206nb2) is linked into the standard
> > > view, while the -current version of lynx (220.127.116.11.7nb3) is linked into
> > > the "devel" view.
> > I have question about this.... in the example you are using different
> > directory (views directory I think) to install lynx and lynx-current, but do we
> > can to install them into the same directory? e.g:
> > $ cd lynx; make install
> > $ cd lynx-current; make install
> This sequence of commands will try to install both lynx and lynx-current
> into the standard view. The result will be that lynx will be symlinked
> correctly, while lynx-current will not. The attempt to add lynx-current
> to the standard view will cause a non-fatal error that notes that there
> are some file collisions between lynx and lynx-current.
Shouldn't it appear as an update (they share the same package name)?
I understand the non-fatal error is useful to install conflicting packages
in the same view, but when it is two version of the same package... But I
guess there will be things to fine-grain later when pkgviews gets broader