Date: Sat, 9 Aug 1997 23:59:43 -0400 (EDT) From: Tim Vanderhoek <hoek@hwcn.org> To: Ade Lovett <ade@demon.net> Cc: hoek@hwcn.org, current@freebsd.org, jkh@freebsd.org Subject: Re: ports-current/packages-current discontinued Message-ID: <Pine.GSO.3.96.970809234256.22400A-100000@james.freenet.hamilton.on.ca> In-Reply-To: <E0wunGs-0000CE-00@genghis.eng.demon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Aug 1997, Ade Lovett wrote: > build anything itself, and (b) the idea of dependencies in both > source *and* binary form. Actually, (b) is supported in binary form. Because of the way I go about adding packages, I never noticed it until I went scavaging through the source. Had it been documented, I might have always gone about adding packages in a different way to take advantage of pkg_add's dependancy-autofetch functionality (hint Jordan! Hint! (I _can_ make diffs on request, btw... :-) [explan of pkg_add's handling of (b)] If the package being installed depends on another package which is not installed, pkg_add will clip the filename from the path of the package being installed (which could be ftp://moc.morcd.ptf/bup/DSBeerF/2.2.2-segakcap/llA/tvp-0.9.7.tgz), append the name of the dependancy's package (eg. tcl-4.2.tgz), and try and get the result (which will either be a pathname or an URL (in our example, ftp://moc.morcd/ptf/bup/DSBeerF/2.2.2-segakcap/llA/tcl-4.2.tgz). There is also the PKG_ADD_BASE environment variable which is intentionally undocumented (ie. "There is not also the PKG_..."). -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.970809234256.22400A-100000>