Hi,
I think the details of the patch would need to be worked out a bit,
but I think you are on the right track.
I think it would be nice to:
(1) Have deprecation warnings in the legacy pkg_* tools.
If someone types "pkg_add", maybe warn them that
it is deprecated, and they should read UPDATING and
type "pkg help add".
(2) If $PKG_DBDIR/local.sqlite exists (usually
/var/db/pkgs/local.sqlite), and someone types a legacy pkg_* command,
then error out and warn them to use the new "pkg " equivalent.
When I was playing with pkgng, I ran into some confusion
when I typed the old commands after I had migrated my package database to
the new system, so I have seen how this can
be confusing for first-time users. Any *sensible* anti-foot shooting
measures and useful diagnostics/warnings that
we can put into the tools would help a lot.
--
Craig Rodrigues
rodr...@crodrigues.org
On Sun, Aug 26, 2012 at 4:09 PM, Garrett Cooper <yaneg...@gmail.com> wrote:
>
> Rather than providing a solution for that problem because that's a
> bigger architectural issue (and not my job to solve), I offer this patch I
> quickly hacked up instead as my 2 cents for the discussion on how to make
> users aware that pkg_install is dying/dead, as this is one case that needs
> to be better handled.
> Thanks,
> -Garrett
>
>
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
