Yeah, I will say that pkg_info could get a lot more featureful
than it is now without "exceeding its mandate." It would have
been better than a profusion of tools.
- Jordan
>
>
> On Mon, 26 Jun 2000 00:57:00 MST, Jeremy Lea wrote:
>
> > I've placed the source for a new command, pkg_which, on
Hi,
On Mon, Jun 26, 2000 at 12:30:09PM +0200, Sheldon Hearn wrote:
> Argh, yet another pkg_* command that looks (at first glance anyway) like
> it should have been implemented as a feature enhancement to the existing
> pkg_* tools.
>
> What is it that makes this unsuitable for incorporation into
On Mon, 26 Jun 2000 00:57:00 MST, Jeremy Lea wrote:
> I've placed the source for a new command, pkg_which, on
> http://people.freebsd.org/~reg/.
Argh, yet another pkg_* command that looks (at first glance anyway) like
it should have been implemented as a feature enhancement to the existing
pkg
Jeremy Lea wrote:
> Hi guys,
>
> This is BCC'd to ports, since it is mostly for use there...
>
> I've placed the source for a new command, pkg_which, on
> http://people.freebsd.org/~reg/.
>
> The idea behind this command is to get Ports/Packages to register their
> dependencies based on what is o
Hi guys,
This is BCC'd to ports, since it is mostly for use there...
I've placed the source for a new command, pkg_which, on
http://people.freebsd.org/~reg/.
The idea behind this command is to get Ports/Packages to register their
dependencies based on what is on the system, not what they think
