tech-pkg archive

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

Re: pkg_install in base system again

> Why "pkg_setup"?  Wouldn't you be able to add wrappers for pkg_add,
> etc. that do the right thing on their own, transparently?
My plan was to develop a small tool *both* for NetBSD and non-NetBSD
systems. In general I think separating supported platforms into "NetBSD"
and "others" is not very good idea. Unless someone finishes syspkg
project I don't see any reason to have pkg_* under /usr/sbin.

As I said for "others" pkg_setup can be used for initializing pkgsrc
from binary repositories.

> I.e. check if pkg_install is installed first and, if not, install it.
> Then delegate the original pkg_add call.
Yes, we can add the following logic to the very beginning of pkg_* in

  if (i am /usr/sbin/pkg_tool && /usr/pkg/sbin/pkg_tool){
     run /usr/pkg/sbin/pkg_tool "$@"

unless it adds negative side-effects.
But I'm not sure installing them "transparantly" is a good idea.

> Also, what happens when I check out pkgsrc and I don't have
> pkg_install yet?  Do I have to manually run bootstrap (which is a
> different code path to pkg_setup), or would this pkg_setup know to use
> the pkgsrc sources if they exist?
At the moment pkg_setup is responsible for installing pkg_install from
binary package available on or somewhere.

IIRC David proposed to add an option to pkg_setup for bootstrapping
pkgsrc from sources. I'll do this.

>  Can the mk files in pkgsrc be made
> to do the bootstrapping transparently when needed?
I don't understand your idea.

Best regards, Aleksey Cheusov.

Home | Main Index | Thread Index | Old Index