Date: Fri, 10 Nov 1995 05:41:59 +0000 () From: Michael Smith <msmith@atrad.adelaide.edu.au> To: jbarrm@panix.com (Barry Masterson) Cc: questions@freebsd.org Subject: Re: Installing ported packages Message-ID: <199511100542.FAA11825@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.SUN.3.91.951109213507.20609A-100000@panix.com> from "Barry Masterson" at Nov 9, 95 09:59:03 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Barry Masterson stands accused of saying: > My question is, what part do the 'port' files in play in the > installation of these programs. Should I replace the packaged > Makefile with the ported Makefile? Should I place all of the > 'port' files ( DESCR, PLIST, patches, configure, md5, Makefile.sed,...) > in the same directory as the source code, then 'make'? Put the unaltered distribution archives in /usr/ports/distfiles. Put the 'port' directories in the same arrangement as they are on the FTP site. For example, for rzsz, you would ftp> cd ports/comms ftp> get rzsz.tar.gz ftp> quit # cd /usr/ports/comms # tar xvzf /incoming/rzsz.tar.gz # cd rzsz # make install The ports make process will find the original file in /usr/ports/distfiles (if it's not there, it will FTP it from a known reference site), unpack it, patch it, configure it, compile it and install it. > Barry Masterson -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 041-122-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511100542.FAA11825>