tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg_add and remote packages

> While the current pkg_add(1) does use an external ftp(1) process to
> access remote repositories, there is no "pluggable" interface to let
> you choose a different binary to use.  You can specify one at
> compile-time, but the binary must have the exact same interface as
> ftp(1).
This is good. The only thing you need to do is to
implement a way to change a fetching program by using environment
variable. ftp client (the default) is already in bootstrap.
pkgsrc users can adopt their fetching program to ftp's "API"
(I did the same thing for Interix/ftp/M$ proxy years ago).

> and modernization of the
> pkg_install codebase is definitely a high-priority project.
This is completely different story.

> Joerg's proposed changes now will help make is easier to add new
> features in the future such as the one you're proposing.
I have nothing against modernization, rewtite, refactoring etc.
I just think that using "static" library is VERY bad idea.
And I don't see chicken-and-eggs problem. ftp client, pax are already
in bootstrap.

Best regards, Aleksey Cheusov.

Home | Main Index | Thread Index | Old Index