Date: Fri, 23 Apr 2004 18:43:18 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Danny MacMillan <flowers@users.sourceforge.net> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: updated ports tree Message-ID: <20040424014317.GA21041@xor.obsecurity.org> In-Reply-To: <opr6xtin04rcgix0@shawmail> References: <Sea1-F50X6kLeX78U0O0004fd16@hotmail.com> <opr6xtin04rcgix0@shawmail>
next in thread | previous in thread | raw e-mail | index | archive | help
--envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 23, 2004 at 07:38:37PM -0600, Danny MacMillan wrote: > On Fri, 23 Apr 2004 23:41:36 +0000, Killermink ! <killermink@hotmail.com>= =20 > wrote: >=20 > >I see what your saying and i suppose I have two points: > > > >1) Can you install a port without installing the ports tree? >=20 > Ports can not be installed without first being built, and the ports tree= =20 > is what enables you to build a port. Short answer: no. >=20 > Somewhat longer answer: If your concern is disk space, in theory it woul= d=20 > be possible, I think, to install only that subset of the ports tree=20 > required to build the port you are interested in, but that task is=20 > non-trivial. Most ports depend on other ports, which themselves depend o= n=20 > other ports, and so on. One of the advantages of the ports tree is that= =20 > having it available means you do not have to resolve those dependencies= =20 > manually. I don't think if you install an individual port it would be=20 > smart enough to resolve these dependencies automatically (but I've never= =20 > tried to do it that way). If not, you would have to untar the part of th= e=20 > ports tree containing the port you wish to build, then attempt to install= =20 > it. Then handle each of the inevitable errors in turn, untarring=20 > progressively more of the ports tree until you get it to the point where= =20 > it will install your port. I don't think this is the best way to go, but = I=20 > would be interested to know if and how well it works. >=20 > If you go to http://www.freebsd.org/ports/ you can browse the ports=20 > collection online and download individual tarballs for each port. Each= =20 > port also lists its dependencies so you can see how big of a task you=20 > might be letting yourself in for. The portcheckout port is an easier alternative. > >I am still new at this, and can't seem to find packages for all the=20 > >ports in the tree... >=20 > My understanding is this: That there aren't packages for all the ports i= n=20 > the tree, but that there are many more packages available on the ftp=20 > site(s) than ship on the CD. If you browse the ports collection online= =20 > you'll be able to download packages for many (most?) of the ports. If yo= u=20 > would really rather not install the ports tree, I'd invest some time in= =20 > looking for the package you want to install. Odds are pretty good it's= =20 > available. There are packages for everything that can be packaged automatically and redistributed. If a port is broken, requires manual intervention to build, or may not legally be redistributed, it won't be on the FTP sites. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAicY1Wry0BWjoQKURAvs/AJ0YAG9nRDaxvTHON+1ToJMPGR6XbgCgo8wj lggJ2SayFIjRNBfwRY/S7H0= =NIXX -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040424014317.GA21041>