On Mon, 28 May 2007, Ingo Schwarze wrote:

Hi Antti,

Hi and thanks for your reply.

[snip]
Instead, the syntax specified in ftp(1) is
 ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/]
so you need to specify the password, i.e.
 PKG_PATH=ftp://ftp:[EMAIL PROTECTED]/path/to/packages/

Yeah I read the manual before posting but didn't realize
it needs password too and I was uncomfortable providing
it from the command line.

[snip] By the way, if your packages
are secret, are you sure you want to install them?  On the other
hand, in case you just use wierd non-standard usernames for
anonymous ftp, you are successfully implementing obscurity by
obscurity which is probably a bad idea, too.

For snapshot installation I fetch the whole tree to a server
near by in case I have to install something later on. I
don't want to mix packages from newer snapshots.

Thus, i suggest to just use standard anonymous ftp instead.

Earlier the server in question was in fact anonymous, not anymore.
The source I'm using is and it's official OpenBSD mirror.

sftp:// simply isn't implemented, see the list in
OpenBSD::PackageRepository::new(): ftp, http, scp, src.
By the way, i have no idea why sftp should be quicker than scp.

The reason why I was asking this is that usually sftp:// just works
so I tried it first, took a while to notice I have to specify
"scp".

Still, sftp:// might be useful for servers offering SFTP access
without offering shell access.  Try submitting a patch to
OpenBSD/PackageRepository* if you need it.  The pkg_add part
will probably be easy.  What might be a bother is that sftp(1),
contrary to ftp(1), doesn't appear to support output to stdout(4).

I'm not that much of perl coder 8-)

PS. Isn't there some library/layer/whatever for perl that could be used to
enable protocol independent package fetching? Something like kioslave in kde? I don't see a reason why one would have to implement all url schemes from scratch..

--
Antti Harri

Reply via email to