Date: Tue, 9 May 2000 10:29:12 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Adam <bsdx@looksharp.net> Cc: current@freebsd.org Subject: Re: a better idea for package dependencies Message-ID: <20000509102912.D28677@dragon.nuxi.com> In-Reply-To: <Pine.BSF.4.21.0005091320490.11996-100000@turtle.looksharp.net>; from bsdx@looksharp.net on Tue, May 09, 2000 at 01:23:09PM -0400 References: <20000509075209.D6350@dragon.nuxi.com> <Pine.BSF.4.21.0005091320490.11996-100000@turtle.looksharp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 09, 2000 at 01:23:09PM -0400, Adam wrote:
> >And are only used for Ports. Thus their behavior defines the behavior of
> >the Ports Collection. Thus it is a Ports issue. IF the pkg_* utils were
> >ports, how would you install them??
>
> Am I missing something? I thought ports only need some .mk files and
> make? (Along with tools to get those there, including the port itself, at
> most fetch or ftp, and tar?)
Packages (ie, those things that pkg_{create,add,delete,info} operate on
are created with in /usr/ports. When one builds a port and installs it,
pkg_{create,add} is run on the backend behind your back. If you
``make package'' yourself, you will get a package tarball. These are the
files on the FTP site and CDROM disc in the package/ dir. You install
these by ``pkg_add foo''. You delete the package (ie, the thing built in
/usr/ports) with ``pkg_delete foo''.
Hopefully some day, parts of the /usr/src bits will be installed with the
pkg_* utils, but today only things in /usr/ports are used with the pkg_*
utils.
--
-- David (obrien@NUXI.com)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000509102912.D28677>