Date: Tue, 10 Apr 2001 15:47:44 +0100 From: Rasputin <rara.rasputin@virgin.net> To: questions@freebsd.org Subject: Re: ports vs standard sources Message-ID: <20010410154744.B47021@dogma.freebsd-uk.eu.org> In-Reply-To: <Pine.LNX.4.21.0104101043290.3895-100000@iib005.iib.unsam.edu.ar>; from fernan@iib.unsam.edu.ar on Tue, Apr 10, 2001 at 12:20:51PM -0400 References: <Pine.LNX.4.21.0104101043290.3895-100000@iib005.iib.unsam.edu.ar>
next in thread | previous in thread | raw e-mail | index | archive | help
* Fernan Aguero <fernan@iib.unsam.edu.ar> [010410 15:24]: > Hi all! > > I am new to FreeBSD and just starting to get the grasp of the 'ports' > concept. I have already installed a few and found that is really a great > thing to have. Yeah, they're fantastic aren't they? The easiest installation system on any platform bar none IMO. > However I also noticed that many of them are outdated and No, they get updated daily. You'll need to update them to get the latest ones. Look in the Handbook for the cvsup section, and see /usr/share/examples/cvsup, in particular the ports* files. > i) first of all I thought that ports were necessary because things would > not compile straight otherwise. Nope, a lot of stuff builds fine. The ports just aoutomate a lot of patching, etc , for you. > Then my question is: how do autoconf based compilation work in FreeBSD? - > I mean sources that use GNU autoconf to generate a configure script (that > in turn generates a Makefile)? autoconf works the same in FreeBSd as any other platform. > If autoconf-configure work OK, then the idea of ports is just to help > download-patch-compile in an automated way? Yes. > Another question: I noticed that some ports did run a configure script > before compiling, however, I could not pass any custom option to > configure, since it was all part of the port 'make' procedure. How can I > manually add options before compiling? You don't normally need to if they're ports - in your example below , the PHP port would configure apache for you. If you ever bneed to, you can run make configure then cd into work/<program-name> and edit configure, then go back up to the port directory and type make install > (Example: suppose I want to compile php as an apache module. I would run > configure on php sources like this: ./configure > --with-apache=../apache_1.3.x). How would you this with ports? -- Rasputin Jack of All Trades :: Master of Nuns To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010410154744.B47021>