Re: running portupgrade -a
On Sunday 01 July 2007 17:19:22 [EMAIL PROTECTED] wrote: > On 29/06/07, Michael P. Soulier <[EMAIL PROTECTED]> wrote: > > Hi, > > > > It seems like a lot of people keep their ports regularly up to date by > > just running portupgrade -a. I've seen it online, and in books. > > > > As /usr/ports/UPDATING is rather large, it seems impossible to look for > > potential issues with every package that you're going to upgrade. So, is > > running portupgrade -a a good idea, as you likely haven't checked for > > issues for your system? > > I generally run pkg_version -vIL= after any portsnap > which gives me a simple list of things to upgrade. > Then, based on a lot of broken stuff over the years, > you can merrily pick your way through. For something > like cairo or gtk* (or gettext), that many other things > depend upon I will run > # portupgrade -fr cairo > Part of this is the whole "upgrade once every couple > of weeks or oft'ner" so you don't get overwhealmed > by the number of upgrades at any time. > ports-mgmt/portmaster has a nifty feature in "-l" but > does not seem to have any equivalent to portupgrade -fr. i have another good one for sorting out what needs to be updated: pkg_version -v|grep needs this will show only the ports that need to upgraded. cheers, -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: running portupgrade -a
On 29/06/07, Michael P. Soulier <[EMAIL PROTECTED]> wrote: Hi, It seems like a lot of people keep their ports regularly up to date by just running portupgrade -a. I've seen it online, and in books. As /usr/ports/UPDATING is rather large, it seems impossible to look for potential issues with every package that you're going to upgrade. So, is running portupgrade -a a good idea, as you likely haven't checked for issues for your system? I generally run pkg_version -vIL= after any portsnap which gives me a simple list of things to upgrade. Then, based on a lot of broken stuff over the years, you can merrily pick your way through. For something like cairo or gtk* (or gettext), that many other things depend upon I will run # portupgrade -fr cairo Part of this is the whole "upgrade once every couple of weeks or oft'ner" so you don't get overwhealmed by the number of upgrades at any time. ports-mgmt/portmaster has a nifty feature in "-l" but does not seem to have any equivalent to portupgrade -fr. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: running portupgrade -a
On Fri, 29 Jun 2007 19:14:52 -0400 "Michael P. Soulier" <[EMAIL PROTECTED]> wrote: > Hi, > > It seems like a lot of people keep their ports regularly up to date by just > running portupgrade -a. I've seen it online, and in books. I've been updating ports daily for several years using portupgrade since that seemed the best for me. Doing it on a frequent basis usually keeps the number of ports changing to a smaller number and it seems easier to track down any issues that crop up. > As /usr/ports/UPDATING is rather large, it seems impossible to look for > potential issues with every package that you're going to upgrade. So, is > running portupgrade -a a good idea, as you likely haven't checked for issues > for your system? Its only necessary to check the entries in UPDATING since your last update. If you don't check the entries before updating, its possible that a problem might happen. The more frequent you update, the less new entries there are to check of course. > Otherwise, the ports change so fast that if you don't regularly update, when > you do go to upgrade you may find yourself in a difficult position to do so. Agreed. It may even reach the point where so many ports need updated that it may be just as fast to deinstall all ports and install fresh. Frequent updating also gains you more familarity with the ports system. I don't think there are any tools that are 100% perfect and human errors do happen. HTH Randy -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: running portupgrade -a
Michael P. Soulier wrote: Hi, It seems like a lot of people keep their ports regularly up to date by just running portupgrade -a. I've seen it online, and in books. As /usr/ports/UPDATING is rather large, it seems impossible to look for potential issues with every package that you're going to upgrade. So, is running portupgrade -a a good idea, as you likely haven't checked for issues for your system? Otherwise, the ports change so fast that if you don't regularly update, when you do go to upgrade you may find yourself in a difficult position to do so. Mike, Read the list, read /usr/ports/UPDATING and you're usually quite safe at least with -RELEASE or -STABLE. The FreeBSD ports system is an excellent tool and I have yet to see a better one. You could do the upgrade procedure in many ways, this is what I do, portupgrade -avn - this will show you what could be upgraded. A brief search in UPDATING for issues A brief look in the @ports and @questions perhaps Usually no major hazzles so I just do a portupgrade -av and let it run, if there are any problems on the way I'll go back and fix them afterwards. This would be the typical scenario for my home or work PC's, however, if it's an important production server I always run it on a test box first. Good luck! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: running portupgrade -a
At 07:14 PM 6/29/2007, you wrote: So, is running portupgrade -a a good idea, as you likely haven't checked for issues for your system? I just started using portupgrade recently, and no, I would NOT let it rip with the --all option. I find it's most useful for the libraries and required packages that don't need any compile-time options nor config files. Those sorta things I install from packages anyway. So I started with a list of stuff that required compile time control and/or configuration. "ls /var/db/ports" and pkg-info are a good start... Then run "portupgrade -aiP" -i asks for confirmation on each, and -P tries to get it from packages (binary) rather than ports. Let that update all the "background" junk. Than go back and research and possibly manually remake & install the primary apps (eg: apache, samba, squid, in my case.) HTH, -RW ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: running portupgrade -a
On Fri, Jun 29, 2007 at 07:14:52PM -0400, Michael P. Soulier wrote: > Hi, > > > > > > It seems like a lot of people keep their ports regularly up to date by just > > > running portupgrade -a. I've seen it online, and in books. > > > > > > As /usr/ports/UPDATING is rather large, it seems impossible to look for > > > potential issues with every package that you're going to upgrade. So, is > > > running portupgrade -a a good idea, as you likely haven't checked for issues > > > for your system? > > > > > > Otherwise, the ports change so fast that if you don't regularly update, when > > > you do go to upgrade you may find yourself in a difficult position to do so. > > I check the output of the following portversion command line to see what software will be upgraded if I issue the "portupgrade -a" command: portversion | grep -v = This ensures that packages with up-to-date versions and no special notes are ignored. I then compare that list of packages to the UPDATING file to see if there's anything that requires special attention. The UPDATING file is organized in reverse chronological order. This means that you need only read down as far as the first date in the file that is old enough so you know you've updated since then. Once I have checked the portversion output against the UPDATING file, I run this command:
