svn commit: r243554 - in head/usr.sbin/pkg_install: add create delete info lib updating version
Fabian Keil
freebsd-listen at fabiankeil.de
Fri Dec 21 12:31:27 UTC 2012
Eitan Adler <eadler at freebsd.org> wrote:
> On 28 November 2012 21:34, Stanislav Sedov <stas at freebsd.org> wrote:
> > I don't really see how this
> > message being in pkg_ tools helps to prevent a possible foot-shooting
> > at all.
>
> It reminds people that using the pkg_* tools once a conversion is done is wrong.
I don't see how that prevents foot-shooting either.
Is there a single case where running one of the pkg_* tools
is dangerous and spamming the console somehow mitigates this?
How is the following helpful?:
# pkg2ng
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
Creating backup pkg_info(1) database directory in /var/db/pkg.bak.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
Installing adns-1.4_1... done
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
pkg_info: You appear to be using the newer pkg(1) tool on this system for package management, rather than the legacy package management tools (pkg_*). The legacy tools should no longer be used on this system.
Installing autoconf-2.68... done
[...]
> > At very least, it makes sense to make it conditional on WITH_PKGNG, so this
> > code does not end up compiled in if PKGNG is disabled in src.conf.
>
> Interesting idea. Maybe I shall do this.
Yes, please.
Fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-src-all/attachments/20121221/4c9736ec/attachment.sig>
More information about the svn-src-all
mailing list