Re: upgrading all ports
On Monday 27 June 2005 17:37, Denny White wrote: On Mon, 27 Jun 2005, RW wrote: On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. ... This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. You can break-out of portupgrade -arRF anytime you like, it's only fetching distfiles not upgrading anything. Normally portupgrade -Fa will fetch all the file you needs, but portupgrade -FRa is a bit more thorough. Really though you don't need to run with the -F option at all, unless you can't build online or want to prefetch files. If it's taking 40 hours though, it probably means that your cache of files is badly out-of-date and you are getting slow downloads - a clean pass that doesn't fetch anything shouldn't take more than a hour. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 28 Jun 2005, RW wrote: On Monday 27 June 2005 17:37, Denny White wrote: On Mon, 27 Jun 2005, RW wrote: On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. ... This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. You can break-out of portupgrade -arRF anytime you like, it's only fetching distfiles not upgrading anything. Normally portupgrade -Fa will fetch all the file you needs, but portupgrade -FRa is a bit more thorough. Really though you don't need to run with the -F option at all, unless you can't build online or want to prefetch files. If it's taking 40 hours though, it probably means that your cache of files is badly out-of-date and you are getting slow downloads - a clean pass that doesn't fetch anything shouldn't take more than a hour. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I finally broke out of it. I waited until it had done its cleaning was starting to fetch more files. I did a ls -alt on /var/db/pkg it was definitely installing/ reinstalling ports. Won't do that again. :) I had wanted to force the upgrade or downgrade, whatever, of several held ports. Now I think maybe it had something to do with me not updating perl the right way. My bad. I went back reread UPDATING found what I had missed. I did a man perl-after-upgrade reread all of that too followed the instructions. Looks like everything's back to normal. Thanks for the help. Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwW4cy0Ty5RZE55oRAkAKAKCYmKfN8PabPGawUE5M6FQqZBIm+QCdFCsU MTCJr7cUxTcCipfZH/uDvjY= =h6sQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. Portmanager is a good way to bring your ports up-to-date, but it also rebuilds all ports that depend on out-of date ports. It's a very slow process if you have a slow machine and most of your ports were up-to-date already, but try it for yourself. Portupgrade does a pretty good job if you follow UPDATING, and use the gnome script for major Gnome upgrades. If you want to force the rebuilding of all your ports then see pkg_glob(1) and portupgrade (1) for instructions on how to rebuild ports built after a given timestamp, as this gives you a restartable method. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
Is there a way to do all of this with packages, I've used ports system exclusively? The reason I ask is... well I don't like waiting 2 to 3 days for everything to rebuild and I take the defaults for most programs anyways. if I could do that and then just rebuild the apps I want with custom flags that would be cool... pkg_version -v says I have 176 out of date ports. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Monday 27 June 2005 16:39, Nikolas Britton wrote: Is there a way to do all of this with packages, I've used ports system exclusively? The reason I ask is... well I don't like waiting 2 to 3 days for everything to rebuild and I take the defaults for most programs anyways. if I could do that and then just rebuild the apps I want with custom flags that would be cool... pkg_version -v says I have 176 out of date ports. You can do it to a limited extent using portupgrade with the -P and -PP options, or the settings in pkgtools.conf. The trouble is finding a suitable source of packages, I've upgraded KDE this way using the fruitsalad servers at freebsd.kde.org, but the ordinary FreeBSD servers don't keep packages up-to-date for releases. It might work for 5-stable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, RW wrote: On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? AFAIK there is no difference between the two; -a means upgrade all ports in the package database, -Rr means add in the dependencies and dependent ports based on what's in the database, but these are already covered by -a. New dependencies are built as a side-effect of building out-of-date ports - not through the -R option. There *is* a difference between -FRa and -Fa because -FR is translated into a make checksum-recursive. Anyone who believes that portupgrade is slower than removing all port and reinstalling has probably been misled by watching portupgrade -FRa which runs make checksum-recursive for each installed port and so visits some ports many time. Portmanager is a good way to bring your ports up-to-date, but it also rebuilds all ports that depend on out-of date ports. It's a very slow process if you have a slow machine and most of your ports were up-to-date already, but try it for yourself. Portupgrade does a pretty good job if you follow UPDATING, and use the gnome script for major Gnome upgrades. If you want to force the rebuilding of all your ports then see pkg_glob(1) and portupgrade (1) for instructions on how to rebuild ports built after a given timestamp, as this gives you a restartable method. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. Any help/feedback on this will be GREATLY appreciated. :) Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwCs6y0Ty5RZE55oRAj6LAJ4wuENN2VAn5IlWUeRsPVps5nBgcQCgtsRr +YpDWuFkojneBoJkl3qk4Jk= =DrUN -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On 6/27/05, Denny White [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, Nikolas Britton wrote: This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. Any help/feedback on this will be GREATLY appreciated. :) Denny White You shouldn't have any problems if you do that but kill it at the beginning of the next build, not when it's cleaning. Thanks so much for the personal speedy reply. I've worked for a month getting this system to about where I want it, I hate to see it all go down the tubes. Sure glad you straightened me out on when to break out, too. I see you didn't put in a cc to freebsd-questions, so I guess I won't either. After breaking out of the loop, what's the best thing to do at that point? The only way I could come up with to try to start is: cvsup ports-supfile portsdb -Uu portversion -l portupgrade -arR (no F this time) Just restart portupgrade without the F flag, it will pick-up where it left off. If I can get things back right, I'll just learn to live with the held ports. I never remember telling it to hold anything, it's probably pretty apparent I don't understand as much as I should about portupgrade. I learned what I know from Dru Lavigne's blogs at Oreilly, until I fat-fingered the F without thinking, it was working okay, except for the held ports. Thanks again for your help. Denny White I'm not sure what you mean by held ports? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, Nikolas Britton wrote: On 6/27/05, Denny White [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jun 2005, Nikolas Britton wrote: This couldn't have come at a better time for me. I really boned things up about 40 hours ago. I was getting ready to leave and because I'd been doing some learning/experimenting with portupgrade on some held ports, I hit the wrong switch. I think it was portupgrade -arRF now, about 40 hours later, shortly after returning home, we're still going, going, going... Things are really in a mess I've read the recent posts on this thread can attest, sitting here for several hours, that visits some ports many times is an understatement. It's becoming rediculous I'm wondering if, at some point, when clean is going after something else was just upgraded, if I can break out go back with a simple portupgrade -arR not screw things up to badly. Any help/feedback on this will be GREATLY appreciated. :) Denny White You shouldn't have any problems if you do that but kill it at the beginning of the next build, not when it's cleaning. Thanks so much for the personal speedy reply. I've worked for a month getting this system to about where I want it, I hate to see it all go down the tubes. Sure glad you straightened me out on when to break out, too. I see you didn't put in a cc to freebsd-questions, so I guess I won't either. After breaking out of the loop, what's the best thing to do at that point? The only way I could come up with to try to start is: cvsup ports-supfile portsdb -Uu portversion -l portupgrade -arR (no F this time) Just restart portupgrade without the F flag, it will pick-up where it left off. If I can get things back right, I'll just learn to live with the held ports. I never remember telling it to hold anything, it's probably pretty apparent I don't understand as much as I should about portupgrade. I learned what I know from Dru Lavigne's blogs at Oreilly, until I fat-fingered the F without thinking, it was working okay, except for the held ports. Thanks again for your help. Denny White I'm not sure what you mean by held ports? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Held ports are listed in an array in /usr/local/etc/pkgtools.conf. Why I have any there beats me. I don't know enough about it yet to be able to give an answer. There are times when portupgrade will ask me questions about extra features in some port, but that's the only interaction I remember having with the program while it was running, as far as supplying answers to it. I never remember telling it to hold anything. Wish someone could help me get this through my thick noggin. :) I've been doing a lot of reading on it, I see where a lot of folks think you're better off deinstalling ports starting from scratch. Others prefer portsmanager, I think it's called. The reason I started using ports in the 1st place was to learn how to add extra features to progs that aren't installed by default, as in packages. Since I definitely ain't that sharp, I may start using pkgs more ports less. I'd rather have a smooth working install than the power to wipe out my system have to reinstall, at least until I ever get up to speed on things. Thank you very much for the help. Denny White -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwFloy0Ty5RZE55oRAqiDAJ44tORnQYQY7QA1o5fMDxFSouurRQCg0aNc aZRTHj3B/y0nmcbP8bhb3FE= =bDDM -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
Kirk Strauser wrote: On Saturday 25 June 2005 06:36 am, Erik Nørgaard wrote: It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. On toy systems, maybe. I've got 654 ports installed on the machine I'm typing this on, and I assure you that it's much, much faster to selectively upgrade a few of them rather than starting over from scratch. I think you overlooked one important thing in the original post, and in my post as well: We are talking about upgrading the entire system, not just a few ports. Upgrading a few ports is faster using portupgrade, yes. Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sat, 25 Jun 2005, Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? I hesitate and don't want to screw up my machine. # portupgrade -a works fine, if you do it regularily, i.e. there isn't too much to be updated and thus not too much that could be messed up. Before you start you should check /usr/ports/UPDATING if there are any ports that need special treatmentâand make sure # pkgdb -F doesn't show any inconsistencies. Good Luck, Uli. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] * * Peter Ulrich Kruppa - Wuppertal - Germany * *___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sunday 26 June 2005 06:28 am, you wrote: We are talking about upgrading the entire system, not just a few ports. It really depends on how often you upgrade. If more than once a year or so, I maintain that portupgrade -a is faster than the OpenBSD-style uninstall and reinstlal process. -- Kirk Strauser pgpWLLCRSLTgP.pgp Description: PGP signature
Re: upgrading all ports
Alex Zbyslaw wrote: Erik Nørgaard wrote: portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. What, in your opinion, makes it unsuitable? I've used portugrade exclusively and never had trouble. Unsuitable if - it is slower than the altertative to deinstall all ports and reinstall. - thinks break I don't claim it won't work, I don't claim that things will break, but they may depending on what is being upgraded which was not mentioned in OP. The problem is that the double (up and down) recursive resolution of interdependencies quickly becomes very complex with the result that some ports may be updated multiple times, or that portupgrade will choke trying to figure out where to start. It then quickly becomes much faster to simply deinstall all ports and reinstall. It also lets you clean up any junk that may have been left for whatever reasons. And, then there are the general warnings about upgrading Gnome (not minor minor upgrades) eg 2.8 to 2.10, upgrading perl and friends, module paths etc. These are things that can ofcourse be resolved, I just found it easier to clean up the whole thing and reinstall it, see /usr/ports/UPDATING - there are numerous warnings on portupgrade. For single/few apps upgrade portupgrade is fine, or if the system is mostly up to date so a full upgrade will only affect a few packages. I have had my system serverely down after using portupgrade because of problems with dependencies on X11. OP did not mention how old the system to be upgraded is. So in the particular case it is dificult to say. But I assume that if he wants to upgrade his _entire_ system then I can assume significant updates to be done. Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On 6/25/05, Erik Nørgaard [EMAIL PROTECTED] wrote: portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. I recommend writing down a list of apps you need to be happy, deinstall everything and then install those apps. Dependencies comes along fine, and then whatever remains can be installed as needed. Anyway, the worst that can happen is that you will screw up some user app's - ok this is bad - but your system won't require a reinstall :-) Cheers, Erik With Gnome, KDE, etc. I completely agree with you, portupgrade always manages fudge something up. What are some easy ways to do this... lets say for example I updated to gnome 2.12 what would be an easy (automated) way to remove all of Gnome 2.10 and all of my GTK apps without removing KDE and my QT apps? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sun, 26 Jun 2005, Nikolas Britton wrote: On 6/25/05, Erik Nørgaard [EMAIL PROTECTED] wrote: portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. I recommend writing down a list of apps you need to be happy, deinstall everything and then install those apps. Dependencies comes along fine, and then whatever remains can be installed as needed. Anyway, the worst that can happen is that you will screw up some user app's - ok this is bad - but your system won't require a reinstall :-) Cheers, Erik With Gnome, KDE, etc. I completely agree with you, portupgrade always manages fudge something up. What are some easy ways to do this... lets say for example I updated to gnome 2.12 what would be an easy (automated) way to remove all of Gnome 2.10 and all of my GTK apps without removing KDE and my QT apps? You should download download the gnome upgrade script from www.freebsd.org/gnome and use it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] * * Peter Ulrich Kruppa - Wuppertal - Germany * *___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
upgrading all ports
I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? I hesitate and don't want to screw up my machine. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Sat, 25 Jun 2005 13:22:56 +0200 Dick Hoogendijk [EMAIL PROTECTED] wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? I hesitate and don't want to screw up my machine. do you want to upgrade all upgradable ports on your machine ? i use portmanager -u and/or portupgrade -arvy i've started using portmanager since i've read good things about it many times, and it does indeed handle dependencies better than portupgrade however, if portmanager ends up with errors i use e.g. portupgrade -rf postgrey* to correct those errors i like the combination of both ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
Dick Hoogendijk wrote: I want to do a portupgrade on all installed ports. What's the right way? portupgrade -arR ? or portupgrade -a ? I hesitate and don't want to screw up my machine. portupgrade isn't suitable for upgrading the entire machine, even though you do recursive and Recursive. It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. I recommend writing down a list of apps you need to be happy, deinstall everything and then install those apps. Dependencies comes along fine, and then whatever remains can be installed as needed. Anyway, the worst that can happen is that you will screw up some user app's - ok this is bad - but your system won't require a reinstall :-) Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading all ports
On Saturday 25 June 2005 06:36 am, Erik Nørgaard wrote: It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. On toy systems, maybe. I've got 654 ports installed on the machine I'm typing this on, and I assure you that it's much, much faster to selectively upgrade a few of them rather than starting over from scratch. -- Kirk Strauser pgpXBLDkTdhIz.pgp Description: PGP signature
Re: upgrading all ports
On 25 Jun Kirk Strauser wrote: On Saturday 25 June 2005 06:36 am, Erik Nørgaard wrote: It is much faster to deinstall everything and then installing from ground up. And it is far more secure in not screwing up. On toy systems, maybe. I've got 654 ports installed on the machine I'm typing this on, and I assure you that it's much, much faster to selectively upgrade a few of them rather than starting over from scratch. I agree. Normally I go over usr/ports/UPDATING and handle the 'problem' cases. After that I do parts, like portupgrade -rR 'XFree86*', etc.. Never a problem. Sometimes I forget to use the -m BATCH=yes option and that's no fun. Options I really want are in my pkgtools.conf zo I don't need the selection screens.. I see no harm in using this -m switch like someone else wrote in this list. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
