Re: suggestion: Host fly-off between pkgin and nih and subsequent official integration

[Thomas Cort <linuxgeek%gmail.com@localhost>]

> yes, but that was sort of the point of this thread.  If one of these
> was just "forced" on everyone rather than optionally installed, pkgsrc
> would be at its best.  Obviously SmartOS is doing exactly this.

Minix does this too. The default install comes with pkgin. It works
well. There's no problem using it to update itself nor pkg_install. I
don't believe we chose pkgin over nih for any other reason than pkgin
required less porting.

> 1) the chroot and pbulk building is incredibly cumbersome to set up
> the documentation seems to be outdated on top

Minix has two scripts which strive to automate this so that we can get
consistent/repeatable builds against a current and clean base system.
pbulk.sh[1] handles bootstrapping /usr/pbulk, building the binary
bootstrap kit, and doing the bulk build. pbulk-jail.sh[2] sets up a
chroot and runs pbulk.sh inside it. You can build all of the Minix
packages in a chroot from scratch with one command "sh pbulk-jail.sh
-A". Note, the pbulk.sh script is a bit Minix specific as it has to
work around the fact that Minix doesn't provide compilers in the base
system (we use gcc44 and clang from pkgsrc).

Thomas

[1] http://git.minix3.org/?p=pkgsrc.git;a=blob;f=minix/pbulk.sh;hb=HEAD
[2] http://git.minix3.org/?p=pkgsrc.git;a=blob;f=minix/pbulk-jail.sh;hb=HEAD