Subject: Re: pkgsrc and already installed binary pkgs
To: None <port-i386@netbsd.org>
From: Fernando Machado <fm-nospam@fmachado.com>
List: port-i386
Date: 05/31/2004 17:53:45
Hi magnus,
Did you tried "make update"? e.g.
---installing pthread-sem...-----------------
heaven# pwd
/usr/pkgsrc/devel/pthread-sem
heaven# make install
===> Checking for vulnerabilities in pthread-sem-1.0
===> Installing for pthread-sem-1.0
===> pthread-sem-1.0 is already installed - perhaps an older version?
*** If so, you may use either of:
*** - "pkg_delete pthread-sem-1.0" and "/usr/bin/make reinstall" to upgrade
properly
*** - *"/usr/bin/make update"* to rebuild the package and all of its dependencies
*** - "/usr/bin/make replace" to replace only the package without re-linking
*** dependencies, risking various problems.
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/devel/pthread-sem
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/devel/pthread-sem
*** Error code 1
Stop.
make: stopped in /usr/pkgsrc/devel/pthread-sem
------------------------------------------
Don't forget to update your pkgsrc:
-- bof update-pkgsrc.sh -----
#!/bin/sh
cd /usr/pkgsrc
make clean
export CVSROOT=anoncvs@anoncvs.NetBSD.org:/cvsroot
export CVS_RSH=ssh
cvs -q update -dP
-- eof update-pkgsrc.sh -----
More info about pkgsrc in
www.netbsd.org/Documentation/software/packages.html#binary
Cheers,
-fmac
magetoo@fastmail.fm wrote:
> Hi guys.
>
>
> First of all, apologies if this is slightly off topic. I don't know
> exactly where it belongs.
>
> I've been running 1.6 for some time now, and have always used binary
> packages (off CD). After getting my DSL connection, I'm thinking of
> upgrading, and of using pkgsrc instead of binary packages.
>
> Or more truthfully, I saw something cool and just had to have it, and
> pkgsrc was conviniently there.
>
>
> Now, source and binary packages don't seem to interact too well. Is
> that the way it is supposed to be? The normal routine is that i cd to
> some/package, make, and wait for the error message, which is usually
> "somepackage requires somelib version 1.2.3, but it seems you already
> have somelib 1.1.1 installed (old version?)"; and then pkg_delete -f
> somelib and "make" again. Not exactly optimal, I think.
>
> Especially with packages with lots of dependencies. I don't really
> like having to rebuild something big like, say, Mesa, just to get xmms
> working (which "packagely broke" after updating pth (which had to be
> built so I could use Gaim)).
>
> It will get easier in time, after all the big packages are built, but
> is there a better solution?
>
> This whole thing reminds me of my Debian experience, only back then I
> didn't even have dialup. Thanks to the fast connection it's a lot less
> painful now.
>
>
> Magnus
>
>
>