Re: [6.3] Keeping host up to date
On Sat, 03 May 2008 18:07:08 +0300, Manolis Kiagias [EMAIL PROTECTED] wrote: You just need the ports-supfile. The standard supfile is for the base system. Thanks. I updated the packages I actually need. Looks like I need to run make clean before make config ; make; make deinstall ; make reinstall, otherwise make doesn't do anything: # pkg_version -l [...] php5-5.2.5_1 needs updating (port has 5.2.6) php5-bz2-5.2.5_1 needs updating (port has 5.2.6) php5-ctype-5.2.5_1 needs updating (port has 5.2.6) etc. # cd /usr/ports/lang/php5 # make # ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] Keeping host up to date
On Saturday 03 May 2008 17:07:08 Manolis Kiagias wrote: Gilles wrote: Hello I have some newbie questions: 1. Am I right in understanding that running make ; make install in /usr/ports/ turns the port into a package, so that when I run pkg_info, it doesn't make any difference whether a package was downloaded directly from the Net or compiled locally through the Ports collection? When you compile a port, a package is created and installed (but you get to select the options. Pre-built packages have the default options and are usually older versions). In fact, you can even use the ports to create packages and install them on other systems. (See man ports) Probably the most confusing thing for someone new to the ports system is: - that a port that gets installed is referred to as a package - that a tarball containing the compiled files to install a port is also called a package. When you compile and install a port, a tarball is NOT created. The 'make package' target will do this for you. Also, pre-built packages from FreeBSD-servers have the default options, or more to the point the options that are set by the PACKAGE_BUILDING switch in the port's Makefile if present. But since you can make your own packages, it is perfectly ok to use a build 'server' and upgrade 'client' machines using your own packages and your own options. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[6.3] Keeping host up to date
Hello I have some newbie questions: 1. Am I right in understanding that running make ; make install in /usr/ports/ turns the port into a package, so that when I run pkg_info, it doesn't make any difference whether a package was downloaded directly from the Net or compiled locally through the Ports collection? 2. When I run pkg_version -v, some of the packages are out of date. Generally speaking, what is the safe way to update a package? I'm worried about compiling a new version of a ports that will break the one I already have up and running. 3. Do I really need to run both csup standard-supfile ; csup ports-supfile to update my ports collection? What's the difference between the two? Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [6.3] Keeping host up to date
Gilles wrote: Hello I have some newbie questions: 1. Am I right in understanding that running make ; make install in /usr/ports/ turns the port into a package, so that when I run pkg_info, it doesn't make any difference whether a package was downloaded directly from the Net or compiled locally through the Ports collection? When you compile a port, a package is created and installed (but you get to select the options. Pre-built packages have the default options and are usually older versions). In fact, you can even use the ports to create packages and install them on other systems. (See man ports) 2. When I run pkg_version -v, some of the packages are out of date. Generally speaking, what is the safe way to update a package? I'm worried about compiling a new version of a ports that will break the one I already have up and running. There are programs to automate and safeguard the upgrade. Look at ports-mgmt/portupgrade 3. Do I really need to run both csup standard-supfile ; csup ports-supfile to update my ports collection? What's the difference between the two? Thank you. No. You just need the ports-supfile. The standard supfile is for the base system. Assuming you are running a -RELEASE version of FreeBSD and you just want to get the latest security fixes and patches for the base system, you only need to use the freebsd-update utility. It is as simple as this: freebsd-update fetch freebsd-update install ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
