One more note on this, you actually can't use pkg_* tools *exactly* like you would for packages, you will have to set PKG_DB_DIR (I think) by hand to/var/db/syspkg when you use it. But the plan (as far as I understand it) is to remove the need to that, too; if I'm not mistaken, the first pkg'ized netbsd should be 2.something (former 1.7 ? the next major thing:) At current it's mostly usable only for micro update when you know what you're doing (tm) as the dependancies are somewhat... weak. But still, nothing holds you back from testing some... especially if you have more than one system you can easily build on one, and install, for example, comp-gcc-1-6-M (or something like that - the release version including all minor stuff goes into the package name) on other machines if you know that you will want a new gcc on other machines but not all other stuff from the comp.tgz set. Again, it's not in the release yet, it's not (yet) advocated, I think there's a reason for it:) Not holding ME back at least from sniffing into it (and I enjoy(ed) the tour).
Slashdot Mirror
Check
http://www.netbsd.org/Changes/#nr-scheme-changes
Before it was
0.8 (#1), 0.9 (#2), 1.0 (#3), 1.1 (#4), 1.2 (#5), 1.3 (#6), 1.4 (#7), 1.5 (#8), 1.6 (#9)
as can be seen on
http://www.netbsd.org/Misc/history.html
-> 2.0 (#10)
Regards
Given the style and tone on here, is it surprising to anyone ?
One more note on this, you actually can't use pkg_* /var/db/syspkg when you use it. But the plan (as far as I understand it) is to remove the need to that, too; if I'm not mistaken, the first pkg'ized netbsd should be 2.something (former 1.7 ? the next major thing :) At current it's mostly usable only for micro update when you know what you're doing (tm) as the dependancies are somewhat ... weak. But still, nothing holds you back from testing some... especially if you have more than one system you can easily build on one, and install, for example, comp-gcc-1-6-M (or something like that - the release version including all minor stuff goes into the package name) on other machines if you know that you will want a new gcc on other machines but not all other stuff from the comp.tgz set. :) Not holding ME back at least from sniffing into it (and I enjoy(ed) the tour).
tools *exactly* like you would for packages, you will have to set PKG_DB_DIR (I think) by hand to
Again, it's not in the release yet, it's not (yet) advocated, I think there's a reason for it