Need more help on this topic? This article has Show me There are in this Diary. Only a few deal specifically with upgrading your ports. This article beats them all! Imagine, if you will, a command which allows you to upgrade all of your ports. Stop thinking about make install distclean. No, I mean one command to upgrade each and every port!

FreeBSD how to rebuild all p5-* Perl 5 ports. Up vote 6 down vote favorite. How can I automatically install Perl modules from ports in FreeBSD? It is recommended that to keep FreeBSD systems up to date with the latest application security patches installed via ports collection. The yum command line tool is.

This isn't fantasy or fiction. And it's called portupgrade. I first heard about this great new tool a few months ago, but I never used it until wrote about it in. This was the first time I've read about portupgrade. Coincidentally, I was just starting to install some new ports on in preparation for I was going to give at a local.

It wouldn't do if I gave my presentation on a Windows box. What I will be giving here will be an overview. You really should read Michael's article first. The problem The is one of the best features I can think of.

It's a great way to install software. Fortunately, software gets updated. Unfortunately, some ports expect a certain version of software.

When they don't find it, they can sometimes get very uncooperative and refuse to run. When you upgrade a port and force the install (I'll provide an example later), sometimes other ports which depend on that newly upgraded port will break. It can become a vicious cycle, upgrading one port after another as they dependencies flow outwards. Fortunately, portupgrade does this for you. Pkg_version is your friend when it comes to seeing what ports are up to date. Of course, that does depend upon a recent cvsup of your ports tree. This is pretty easy to do: # cvsup /usr/share/examples/cvsup/ports-supfile -h cvsup.yourhost. Dirty Projectors Bitte Orca Blogspot Rar. org where cvsup.yourhost.org is your favorite cvsup mirror.

Please refer to in the. Here's an example of [manually] upgrading a port upon which other ports are dependant. In this case, I've tried to upgrade devel/glib12 and I'm not upgrading a port, I'm just reinstalling the same version of an already installed port.

Not very useful, but it does illustrate part of the problem. ===>Installing for glib-1.2.10_4 ===>glib-1.2.10_4 is already installed - perhaps an older version?

If so, you may wish to ``make deinstall' and install this port again by ``make reinstall' to upgrade it properly. What Is The Patch Of Hair Under The Lip. If you really wish to overwrite the old port of glib-1.2.10_4 without deleting it first, set the variable 'FORCE_PKG_REGISTER' in your environment or the 'make install' command line. *** Error code 1 Stop in /usr/ports/devel/glib12. *** Error code 1 Stop in /usr/ports/devel/glib12.

[root@laptop:/usr/ports/devel/glib12] # You could try doing a pkg_delete, but then you'd get this: # pkg_delete glib-1.2.10_4 pkg_delete: package `glib-1.2.10_4' is required by these other packages and may not be deinstalled: xchat-1.7.8 imlib-1.9.11 fnlib-0.5 gtk-1.2.10 enlightenment-0.16.5_5 ORBit-0.5.7 And you could do a pkg_delete -f glib-1.2.10_4, but that would mess with the port database ( /var/db/pkg). The ports listed above would then be referencing a version of glib which is no longer installed. If we were actually installing a new version of the port, the dependant ports would be pointing at glib-1.2.10_4 instead of the newly installed version. Two versions of the same port Sometimes you can wind up with two versions of the same port installed. For example: # pkg_info grep m4 m4-1. Xerox Phaser 3435 Driver there. 4 GNU's m4 m4-1.4_1 GNU's m4 /usr/local/sbin/pkgdb -F is your friend.

For simplicity, I'll only show the interesting bits. # /usr/local/sbin/pkgdb -F [Rebuilding the pkgdb in /var/db/pkg. - 34 packages found (-0 +34)....

Done] Checking the origin of BitchX-1.0c18 Checking the origin of apache-1.3.14_1 Checking the origin of autoconf-2.13 Checking the origin of autoconf213-2.13.000227 Checking the origin of bash-2.04 Missing origin. [Updating the ports database in /usr/ports. - 6077 port entries found.1000..2000..3000..4000..5000..6000 (.) done] shells/bash2 (bash-2.05a): Use this? (->shells/bash2) It couldn't find bash. So it went through /user/ports/INDEX and found the right one and updated the database.

For more information on using pkgdb, see. Checking the origin of lynx-2.8.4d9 Missing origin. Www/lynx (lynx-2.8.4.1): Use this? (->www/lynx) Then it did similar for lynx.