Date: Mon, 17 Jan 2000 12:53:43 -0800 (PST) From: patl@phoenix.volant.org To: Omachonu Ogali <oogali@intranova.net> Cc: ports@freebsd.org Subject: Re: What's happened to the rc5des port Message-ID: <ML-3.4.948142423.9799.patl@asimov.phoenix.volant.org> In-Reply-To: <Pine.BSF.4.10.10001161231521.78224-100000@hydrant.intranova.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sat, 15 Jan 2000, Pascal Hofstee wrote: > > > On Sat, Jan 15, 2000 at 01:08:58PM -0500, bush doctor wrote: > > > Does anyone know what's happening with the rc5des port? > > > > This one has been renamed to dnetc (distributed.net client) > > /usr/ports/misc/dnetc On 16-Jan-00 at 09:35, Omachonu Ogali (oogali@intranova.net) wrote: > But do we really need it? YES! Binary ports are -very- useful. * By appearing in the ports collection, they make it easy to find and verify FreeBSD support. * When licencing allows it, the distribution tarball can be included on the CD-ROMs; making life -much- easier for folks without fast internet connections. * The port will (usually) ensure that the files are installed into the locations dictated by hier. * The port/package installation mechanism keeps a database of installed packages, along with the contents, making it easy to un-install cleanly. * The port can install additional support files or scripts which might not have been provided by the base tarball. (Example config scripts tuned for FreeBSD, /usr/local/etc/rc.d startup scripts for daemons, etc.) -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ML-3.4.948142423.9799.patl>