pkgng suggestion: renaming /usr/sbin/pkg to
jlaffaye at freebsd.org
Sat Aug 25 09:50:01 UTC 2012
On 8/24/2012 11:57 PM, Doug Barton wrote:
> On 8/23/2012 8:03 PM, Eitan Adler wrote:
>> On 23 August 2012 22:59, Doug Barton <dougb at freebsd.org> wrote:
>>> I tend to agree with Steve here ... we can't be responsible for other
>>> people's poorly written docs.
>> This isn't about poorly written docs. This is the user expecting a
>> tool to exist, which doesn't. Take another example of a sysadmin which
>> rarely installs new systems, installs FreeBSD for the third time, and
>> then gets confused when "pkg install vim" fails.
> Aren't we going to install the pkg package on new systems when they are
> installed? Isn't that (shouldn't that be?) part of the project plan? It
> would be insane for us not to do that, at least for the releases where
> pkg is the default.
True. But when you create jails without the installer, you have to
install pkgng by hand. Hence the /usr/sbin/pkg bootstrap.
>>> You bring up a valid point that we should
>>> keep in mind for our own however. The bootstrapping issue will be the
>>> smallest possible annoyance on a long road of the migration process.
>> The bootstrapping issue is a factor even after the migration :)
> I think that the point I'm trying to make is that it shouldn't be.
>> note that I'm not talking about the mechanism here, I'm trying to
>> avoid "pkg doesn't seem to be installed on my fresh system" becoming a
> The way that we avoid that problem is not to create it for ourselves in
> the first place. :)
> The role of pkg-bootstrap is for those users who have already-installed
> systems that need to do the conversion, or if somehow pkg becomes
> corrupted on the user's system and needs to be reinstalled. That's it.
> I like that you're thinking through the related issues, but in this
> particular case I think you're overthinking it.
More information about the freebsd-ports