1- PKG_PATH : Okay for your explanation about the default OpenBSD PKG_PATH policy. Default path is set to the current directory.
Trying to do any pkg_add -u will fail unless you have pre-downloaded the newest packages to a directory and cd to it, or if you have to manually investigate where the OpenBSD mirrors are, choose one, investigate where you have to set up your PKG_PATH for later use, do it with the correct syntax (don't forget the last trash, or may be that's issue has already been fixed in latest release?), etc, etc. Investigate where are the faqs, mans, information on how to do the job. So a mere mortal new OpenBSD user will pain (as I did) for loong days till understanding the whole thing: How to keep upgraded/updated your system. Really, a pain. There is still a long road to make OpenBSD kind. 2- "pkg_add don't understand stems": It seems to me that pkg_add DON'T understand stems by itself, it relies on calling ftp (default fetch app) to do that job. But if you set a custom FETCH_CMD= to use "dsocks-torify.sh wget + some options" as fetcher (because ftp don't goes via tor as you want to): # FETCH_CMD="/usr/local/bin/fetch-via-wget-xxxx.sh" # PKG_PATH=ftp://ftp.xxxxx.com/OpenBSD/snapshots/packages/i386/ # pkg_add -v -i -n abcde No packages available in the PKG_PATH Can't resolve abcde # It only works if you specify the full file name to instal: # pkg_add -v -i abcde-2.3.0.tgz parsing abcde-2.3.0.tgz Dependencies for abcde-2.3.0 resolve to: vorbis-tools-1.2.0p0, cdparanoia-3.a9.8p0 found libspec c.48.0 in /usr/lib Error from ftp://ftp.xxxxx.com//OpenBSD/snapshots/packages/i386/abcde-2.3.0.tgz:***********************************| 100% --2008-08-13 02:41:17-- ftp://ftp.xxxxx.com//OpenBSD/snapshots/packages/i386/abcde-2.3.0.tgz => `-' Resolving ftp.xxxxx.com... xxx.xxx.xxx.xxx Connecting to ftp.xxxxx.com|xxx.xxx.xxx.xxx|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /OpenBSD/snapshots/packages/i386 ... done. ==> SIZE abcde-2.3.0.tgz ... 43660 ==> PASV ... done. ==> RETR abcde-2.3.0.tgz ... done. Length: 43660 (43K) 0K .......... .......... .......... .......... .. 100% 4.10K=10s 2008-08-13 xx:xx:xx (4.10 KB/s) - `-' saved [43660] abcde-2.3.0: complete # Note: Please let me explain you that I am building an OpenBSD that goes to Internet exclusively via its own tor anonymizer socks4a proxy server, (including updates and contacts to the OpenBSD mirrors, and that's why I am looking for alternates to ftp as ftp as is can't be socksified (why?) to pass through tor, even using dsocks. (I am anyway looking at the new TransPort tor feature that maybe yes it can do the job, and will try later also some other ideas, next week). Mac Frank Bax wrote: > I did not say PKG_PATH must be set. It does not. > > pkg_add DOES work when PKG_PATH is not set; it will look in the current > directory for packages. When installing packages from the cdrom you > purchased, there is no need to set PKG_PATH if you "cd" into the > appropriate directory first. > > PKG_PATH does NOT need to be a remote site. If you manually download > packages with wget or lynx; then you can point PKG_PATH to this > directory and install packages from there. > > pkg_add DOES understand stems. If you download several packages > manually; then set PKG_PATH to the directory you used; "pkg_add *" will > install all packages in that directory. > > > > > macintoshzoom wrote: >> Hi Frank, Marc, all, >> >> SOLVED!: >> The problem was: >> >> 1-You say that a PKG_PATH must be set, as there is no default one. OK >> Anyway, I tested with and without PKG_PATH. >> >> 2-I am testing a FETCH_CMD using wget, which it seems it don't >> understand "stems" as yes ftp does (the default OpenBSD fetcher). >> So for pkg_add via wget I have to specify the package name including >> extension (must test more about this): >> >> # pkg_add -v -i bmp-0.9.7p13.tgz >> blahblah >> bmp-0.9.7p13: complete >> # >> >> Thanks for your help. >> >> May be I got confused by pbrowser which yes, if you don't start it with >> the command -p "PKG_PATH" (or setup the path from its Edit>Package Path >> menu) it fetch everything from OpenBSD.org by default, a clever option >> for newbies. >> >> So, if I don't specify somewhere the PKG_PATH, pkg_add and probably also >> make will not work! >> >> This is why pkg_add didn't understand stems. >> >> BUT this way a newly installed OpenBSD would not be able to install >> anything till the new user finds how to and set-up a PKG_PATH. >> An added pain for new users. >> Why not a preset OpenBSD.org PKG_PATH? >> To minimize and distribute traffic so individual servers are under less >> strain fetching could be done via an automated mirror's load balancer >> system, a metalink system http://www.metalinker.org/ or similar else. >> >> Mac >> >> >> Frank Bax wrote: >>> macintoshzoom wrote: >>>> After updating to OpenBSD 4.4-current (GENERIC.MP), rebuilt userland, >>>> I am preparing my attack to the updating of my installed packages and >>>> ports. >>>> >>>> I got an issue probably related to syntax or eventually to my >>>> sophisticated experimental proxy environment (everything via tor). >>>> >>>> I tested also doing # export PKG_PATH= <empty> , just to let the >>>> system to check for the OpenBSD.org proper site if in need to verify >>>> or fetch something. >>>> >>>> # pkg_add kdelibs >>>> Can't resolve kdelibs >>>> # >>>> >>>> What could be wrong? >>> >>> >>> Where did you get the idea that PKG_PATH=<empty> will search >>> openbsd.org? It does not. >>> _______________________________________________ >>> Openbsd-newbies mailing list >>> [email protected] >>> http://mailman.theapt.org/listinfo/openbsd-newbies >>> >> > > _______________________________________________ > Openbsd-newbies mailing list > [email protected] > http://mailman.theapt.org/listinfo/openbsd-newbies > _______________________________________________ Openbsd-newbies mailing list [email protected] http://mailman.theapt.org/listinfo/openbsd-newbies
