Date: Fri, 22 May 1998 12:25:05 -0400 (EDT) From: Tim Vanderhoek <hoek@hwcn.org> To: Stuart Henderson <stuart@internationalschool.co.uk> Cc: bjc23@hermes.cam.ac.uk, chat@FreeBSD.ORG, Malartre <malartre@aei.ca> Subject: Re: Why installing ports on a computer? Message-ID: <Pine.GSO.3.96.980522122053.7762B-100000@james.hwcn.org> In-Reply-To: <35656B7B.91723614@internationalschool.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
[Added Malartre back to the cc: since I hate it when people begin mucking with the Cc: header] On Fri, 22 May 1998, Stuart Henderson wrote: > the ports collection usually builds in /usr/ports/*/*/work/.. probably > better to have a port_add command (or even modified pkg_add that can > understand .tar.gz of the tree for an individual port, maybe with a > sysinstall interface) that either ftp's to ftp.*.freebsd.org or mounts Bad idea. In order to guarantee a correct port build, you must have a wholly consisten ports tree. Fetching an individual port will often work, but if we start to pretend supporting that, we're just asking for trouble. Whatever is wrong with using CVSup to keep one's ports tree up-to-date? -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.980522122053.7762B-100000>