Re: question about packages installation

[Erik Wikström <erik-wikstrom@xxxxxxxxx>]

On 2006-08-29 14:44, Saverio Iacovelli wrote:
> > setenv PKG_PATH "ftp://url1;ftp://url2";;
>
> Ok, the command work, but perhaps there is still a
> problem of pkgsrc.
> If you install a package contained in
> ftp://packages.stura.uni-rostock.de/pkgsrc-current/DragonFly/1.6.0-RELEASE/i386/All
> directory, and you need install a dependent package
> contained in
> ftp://packages.stura.uni-rostock.de/pkgsrc-current/DragonFly/1.6.0-RELEASE/i386/vulnerable
> directory, then installation of this second package
> fails because pkg_add is in All directory.

It should work, from the pkg_add manual page:

Over time, as problems are found in packages, they will be moved from 
the All subdirectory into the vulnerable subdirectory.  If you want to 
accept vulnerable packages by default (and know what you are doing), you 
can add the vulnerable directory to your PKG_PATH like this:

# export 
PKG_PATH="ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.0/i386/All;ftp://ftp.NetBSD.org/pub/NetBSD/packages/2.0/i386/vulnerable";

(The quotes are needed because semicolon (`;') is a shell 
meta-character.)  If you do this, consider installing and using the 
security/audit-packages package and running it after every pkg_add.

------

They use export but they have another shell so setenv should be correct 
for you. Could you paste the error-message (or whatever) from when you 
try to use pkg_add. A good way is to use script:

# script out.log
# pkg_add <whatever>
# exit

And all the text written to the console since you started script will be 
in the file out.log, then attack that file to a mail.

--
Erik Wikström