On Wed, Aug 22, 2012 at 05:37:54AM -0700, Jeffrey Bouquet wrote:
> I view, rightly-or-wrongly, the mandatory usage of pkgng VS
> /var/db/pkg/portname-number, as somewhat of a showstopper, at least
> without more assurances... I interact daily with /var/db/pkg as
> follows...
>
> using the shells'
There is pkg2ng tool. I think reverse tool could be useful for such
scenario:
1. System packages managed by pkgng
2. pkgng2pkg creates /var/db/pkg structure, for read-only tasks
3. Any soft relying on get info from /var/db/pkg still works (partially,
because of RO).
And then one could learn new CL
I view, rightly-or-wrongly, the mandatory usage of pkgng VS
/var/db/pkg/portname-number, as somewhat of a showstopper, at least
without more assurances... I interact daily with /var/db/pkg as
follows...
using the shells' tab-completion of /var/db/pkg/ to more efficiently
pkg_create, pkg_delete
po
