3 ms·
> but sqlite should be there, as it is being used in the system (if I am correct, at least by pkg, the new package manager). AFAIK, no. PKGNG is intentionally
by nzp 13y ago
> but sqlite should be there, as it is being used in the system (if I am correct, at least by pkg, the new package manager).
AFAIK, no. PKGNG is intentionally not part of base, it's meant to always remain in ports. The reason is that it allows pkg developers to iterate quickly (and this ties nicely into the recent ports infrastructure overhaul efforts). Once something is part of base and goes into a RELEASE it pretty much has to stay frozen apart for security fixes, and this was deemed not flexible enough for pkg. The only thing in base is a shim pkg which on first invocation installs the real thing from ports (and, I think, later just routes everything to it, unless you remove it or change PATH). So nothing in base uses sqlite and it's in ports/packages.
- enduser 13y agoPKGNG is the default (integrated) package managers in 10.0-RELEASE.
- nzp 13y agoIt's the default alright, but that has nothing to do with it being in the base (yes, it's an exception to the rule). You can look it up on the freebsd-ports@, there were somewhat heated discussions concerning this and some other issues. Unless I've missed something, this decision hasn't changed.
- jlgaddis 13y agopkg can also bootstrap itself. I don't have a fresh FreeBSD install w/o pkg already installed but upon first use it basically goes like this: $ pkg foo pkg is not installed. Install it? (y/n) y ... pkg is now installed
- nzp 13y agoRight, that's what I said[1]---there's a shim pkg in base to install pkg proper from ports. The real pkg is in ports so it can receive continuous upgrades, which wouldn't be possible in a RELEASE (or STABLE for the most part) if it were in base. [1] https://news.ycombinator.com/item?id=7114744 https://news.ycombinator.com/item?id=7114744