Re: port upgrading
On Sunday 26 September 2010, Roland Smith wrote: If you are upgrading to another major version of FreeBSD (say 7.x to 8.x), make a list of all used ports with `portmaster -l ports.list`. Then delete all ports before updating the system. After the update, re-install the 'root' and 'leaf' ports from ports.list. A more convenient approach is to run 'portmaster --list-origins' which produces a list of root and leaf ports which you can feed back into portmaster when reinstalling the ports, all the other dependencies should sort themselves out. There is a good description of this in the final example near the bottom of the portmaster man page. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
port upgrading
I'm in doubt. I wanted to bring my ports collection uptodate, so I ran csup -L 2 /root/ports-supfile and that updated my ports collection. At least, I hope so. Then I started googling and found that cvsup is not recommended. Better tot use portsnap (???) And also portupgrade was a no go. I should be using portmaster. Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: port upgrading
On Sun, Sep 26, 2010 at 06:29:17PM +0200, Dick Hoogendijk wrote: Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. IMO if you don't mind compiling your own ports, use portsnap and portmaster. The sequence is like this; 1) Run `portsnap fetch update`, but see (a). 2) Read /usr/ports/UPDATING, and see if any additions to the top of the file apply to you. If so, take appropriate action. 3) If you have local patches to the ports tree, re-apply them if necessary. This is not really recommended but can be handy sometimes. 4) Run `portmaster -a -B -d` (a) When you run portsnap for the first time, or if you have damaged or deleted the contents of /var/db/portsnap, use 'portsnap fetch extract' instead. For me this is part of the weekly routine. Keep an eye on http://www.freshports.org/ to see if there are interesting changes for you. If you are upgrading to another major version of FreeBSD (say 7.x to 8.x), make a list of all used ports with `portmaster -l ports.list`. Then delete all ports before updating the system. After the update, re-install the 'root' and 'leaf' ports from ports.list. Hope this helps. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgppn3aHOTHD4.pgp Description: PGP signature
Re: port upgrading
On 26/09/2010 17:29:17, Dick Hoogendijk wrote: I'm in doubt. I wanted to bring my ports collection uptodate, so I ran csup -L 2 /root/ports-supfile and that updated my ports collection. At least, I hope so. Then I started googling and found that cvsup is not recommended. Better tot use portsnap (???) And also portupgrade was a no go. I should be using portmaster. Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. csup(1) works fine and there's no good reasons not to use it. portsnap(1) also works fine, and there aren't any obvious problems that mean you shouldn't use it either. There is one somewhat subtle difference, which won't affect most people. 'portsnap extract' will blow away any custom files (Makefile.local, extra patches etc.) that you've added to the ports tree. csup(1) leaves them put. Obviously, either of the two methods will revert any modifications you've made to any files already known to be part of the ports tree. Once you've updated the tree, then you've got several choices for updating your installed ports. portupgrade(1) and portmaster(1) are the leading candidates there: portupgrade probably still has the edge on features, although development seems to be stuttering a bit recently. portmaster wins on simplicity -- it's a shell script with no other dependencies -- but still packs an awful lot of good stuff into approximately 3600 lines. Doug B is actively working on it and very responsive to bug reports etc. Really either of those two will serve you well, as will various others I haven't mentioned. Try them out, see which is most to your taste. There isn't any one 'best' solution that everyone is enjoined to use. That's not the BSD way: Tools, not policy. There are several solutions that you can use, and it's up to you to select which one you prefer. Sure, people having strong opinions on the subject have posted their thoughts on various fora, but don't be misled: those are individual opinions, and not an official position. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: port upgrading
On 26-9-2010 19:13, Matthew Seaman wrote: Really either of those two will serve you well, as will various others I like portupgrade. One question about dependencies: if I want to update *one* port I have to run portupgrade -R portname, right. But *when* do I run portupgrade -R ,name c.q. portupgrade -rR name? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: port upgrading
On 26/09/2010 18:50:32, Dick Hoogendijk wrote: On 26-9-2010 19:13, Matthew Seaman wrote: Really either of those two will serve you well, as will various others I like portupgrade. One question about dependencies: if I want to update *one* port I have to run portupgrade -R portname, right. But *when* do I run portupgrade -R ,name c.q. portupgrade -rR name? It depends on what you want to update. 'portupgrade -R name' updates name plus anything name depends on. 'portupgrade -rR name' updates name plus anything name depends on, plus anything that depends on name. In all cases, only ports that have updates available are updated, so if everything in the dependency chain is already up to date, the command (either variant) may do nothing. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: port upgrading
On Sun, 26 Sep 2010, Dick Hoogendijk wrote: I'm in doubt. I wanted to bring my ports collection uptodate, so I ran csup -L 2 /root/ports-supfile and that updated my ports collection. At least, I hope so. Then I started googling and found that cvsup is not recommended. Better tot use portsnap (???) And also portupgrade was a no go. I should be using portmaster. They are judgement calls. csup is one method, portsnap another. portsnap may be faster, and probably should be the default choice any more (lower bandwidth). portupgrade still works, and many of us still use it. For me, it's just that I almost know how to run portupgrade now, and portmaster didn't seem any better when I tried it. Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? This system is FreeBSD8/amd64. This is an overview of what works for me: http://www.wonkity.com/~wblock/docs/html/portupgrade.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: port upgrading
Woh, I'm confused now. Question: what is best used to have an up2date ports collection nowadays? portsnap fetch extract update for the first time after you've setup the FreeBSD for the very first time. As the parameters used, it fetch the ports tree, extract it to /usr/ports and update it. portsnap fetch update every now and then to update the ports tree. In addition, portmanager does a good job in managing ports in terms of install/update of ports. It doesn't required ports index to find out what is installed or needs to upgrade as it scans the ports tree for dependency, every time. This is good because I don't have to deal with the problem of ports index getting corrupted. Because of this, it does required more time to install/update ports compare to portmaster portupgrade. I've recorded some of my experience in using portmanager : http://scratching.psybermonkey.net/2010/01/freebsd-how-to-manage-ports-in-freebsd.html My 2 cents, Edward. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Port upgrading - my way
On Friday 24 September 2004 03:55 pm, W. D. [EMAIL PROTECTED] wrote:
snip
OK, how about adding a cron job by root like this?
(Line will wrap. Everything between '===' on one line)
==
15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org
/usr/share/examples/cvsup/ports-supfile portsdb -Uu pkgdb -fu cd /usr/ports
make index
==
Then in the morning running:
portversion -l
Would this automate things without causing problems?
Any other safe ways to automate the process?
I run a script in a cron job every day (I changed the name of the user
in the script to username - just use whatever path points to your ports
supfile). I am new at scripting, so the out to /dev/null on every
command might be redundant or unnecessary, and some of it probably
isn't coded efficiently, but it works. Also, I still use portindex,
which has been removed from ports, but the script can easily be
modified to use portsdb -Uu. The script also depends on fastest_cvsup
to pick the fastest server (/usr/ports/sysutils/fastest_cvsup).
Here's root's crontab:
# mail any output to username, no matter whose crontab this is
MAILTO=username
#
# run 4am, every day
1 4 * * * /bin/sh /home/username/supfiles/sup
/var/log/crontab.log 21
Here's the script:
#!/bin/sh
# modified from script found:
# http://www.freebsdforums.org/forums/showthread.php?s=threadid=1162
# posted by ajr
TODAY=$(date +%d-%m-%y)
touch /var/log/supscript-$TODAY
SERVER=`/usr/local/bin/fastest_cvsup -q -c us`
if [ ${SERVER} != ]; then
# update ports, for cvsup-without-gui
/usr/local/bin/cvsup -L 2 -h $SERVER /home/username/supfiles/ports-supfile
21 | tee -a /var/log/supscript-$TODAY /dev/null
# update /usr/ports/INDEX and create INDEX.db; machines with lots
# of RAM (64Mb) and swap can use 'portsdb -Uu' as one command,
# but portindex is faster
# !!! portindex is no longer in ports
/usr/local/bin/portindex 21 | tee -a /var/log/supscript-$TODAY /dev/null
/usr/local/sbin/portsdb -u 21 | tee -a /var/log/supscript-$TODAY /dev/null
# check to see if we need any ports upgrading
BODY=`/usr/local/sbin/portversion -v | grep needs`
if [ ${BODY} != ]; then
echo $BODY | mail -s Ports that need upgrading username | tee -a
/var/log/supscript-$TODAY /dev/null
fi
# clean out /usr/ports/*/*/work and any outdated distfiles
# prefer to run this manually
# /usr/local/sbin/portsclean -CD 21 | tee -a /var/log/supscript-$TODAY
/dev/null
fi
Here's my ports-supfile:
#*default host=cvsup10.freebsd.org
# sup script uses output of fastest-cvsup to determine host
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
*default compress
ports-all
I get two emails every day, one of which is the output of the the cron
job, and the other is a verbose list of ports which have newer versions
available. Everything is logged to /var/log/supscript-$TODAY (date on
the end in dd-mm-yy). I run portupgrade manually, as I want to be able
to choose what to upgrade first (and, depending on the changes, it
might not be necessary to upgrade at all).
- jt
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
W. D. wrote: At 23:11 9/24/2004, Donald J. O'Neill wrote: W.D. it's your cron job I'm looking, so I'll talk about it. It would work, probably most of the time. Your example has both portsdb -Uu and make index in it. Just use one, otherwise you're building INDEX-5 twice. Running pkgdb -fu (by the way, make that -uf instead, I know it doesn't make any difference but I look at it and laugh too hard to think about anything else) Yeah, I guess we really want to un-eff the database, rather than eff-up the database. ;^) won't do the trick in the case were you've deleted something and the now missing dependencies were not taken care of. How would one know when this has occurred? Portupgrade's utilities will gripe at you, and not complete their assigned tasks (e.g., you type portsdb -uU and it returns something similar to stale dependency: pkgfoo-2.1 - pkgbar-3.2 run pkgdb manually to fix, or specify -F to force) You're going to have to do pkgdb -fF and manually remove the bad dependencies. I am clueless here. How would one do this if/when it would happen. Y.A.C.A. (Yet Another Classic Article): http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html This time by Michael Lucas, and yes, it's older than the last, but the concepts are there to be found HTH, KDK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
Oh, I must have had Donald's letter go into my bit bucket as I only saw this message with his reply. (Donald, you reply, Touché, as I was just joking.) Anyhow, I did do it Donald's my way and I just like this other way better for some reason. Sorry Curtis On 23 Sep, 2004, at 22:42, Günther Dippe wrote: Hi all, It seems like the message below doesn't belong on this list unless I completely misunderstood the purpose of it. If I'm wrong please let me know. Cheers snipped Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. OK Curtis, What the heck are you doing, we just discussed this, Chris, I know better than this and so do you. You guys are supposed to be doing it my way. I think you're just trying to get in good graces with the list so you show up here instead of getting filtered into the bit bucket. snipped ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
Oh, I must have had Donald's letter go into my bit bucket as I only saw this message with his reply. (Donald, you reply, Touché, as I was just joking.) Anyhow, I did do it Donald's my way and I just like this other way better for some reason. Sorry Curtis On 23 Sep, 2004, at 22:42, Günther Dippe wrote: Hi all, It seems like the message below doesn't belong on this list unless I completely misunderstood the purpose of it. If I'm wrong please let me know. Cheers snipped Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. OK Curtis, What the heck are you doing, we just discussed this, Chris, I know better than this and so do you. You guys are supposed to be doing it my way. I think you're just trying to get in good graces with the list so you show up here instead of getting filtered into the bit bucket. snipped ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
On Friday 24 September 2004 04:35 pm, Curtis Vaughan wrote: Oh, I must have had Donald's letter go into my bit bucket as I only saw this message with his reply. (Donald, you reply, Touché, as I was just joking.) Anyhow, I did do it Donald's my way and I just like this other way better for some reason. Sorry Curtis Curtis, Don't be sorry for picking a way you like better. I do the samething myself. I just was having a bit of fun. Maybe I'll have to try using portupgrade again and see how it roughly compares to make index. Don -- Donald J. O'Neill [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
At 14:44 9/23/2004, Chris, wrote: You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. -- Best regards, Chris OK, how about adding a cron job by root like this? (Line will wrap. Everything between '===' on one line) == 15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org /usr/share/examples/cvsup/ports-supfile portsdb -Uu pkgdb -fu cd /usr/ports make index == Then in the morning running: portversion -l Would this automate things without causing problems? Any other safe ways to automate the process? Start Here to Find It Fast! - http://www.US-Webmasters.com/best-start-page/ $8.77 Domain Names - http://domains.us-webmasters.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
W. D. wrote: At 14:44 9/23/2004, Chris, wrote: You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. -- Best regards, Chris OK, how about adding a cron job by root like this? (Line will wrap. Everything between '===' on one line) == 15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org /usr/share/examples/cvsup/ports-supfile portsdb -Uu pkgdb -fu cd /usr/ports make index == Then in the morning running: portversion -l Would this automate things without causing problems? Any other safe ways to automate the process? Start Here to Find It Fast! - http://www.US-Webmasters.com/best-start-page/ $8.77 Domain Names - http://domains.us-webmasters.com/ I tend to do this in a periodic cron. Under /etc/periodic/weekly. That also includes the output of portversion to the email. Then in the morning, I run the upgrade. -- Best regards, Chris All things come to him whose name is on a mailing list. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
On Friday 24 September 2004 06:32 pm, Chris wrote: W. D. wrote: At 14:44 9/23/2004, Chris, wrote: You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.htm l An excellent tutorial/article by Dru Lavigne Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. -- Best regards, Chris OK, how about adding a cron job by root like this? (Line will wrap. Everything between '===' on one line) == 15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org /usr/share/examples/cvsup/ports-supfile portsdb -Uu pkgdb -fu cd /usr/ports make index == Then in the morning running: portversion -l Would this automate things without causing problems? Any other safe ways to automate the process? I tend to do this in a periodic cron. Under /etc/periodic/weekly. That also includes the output of portversion to the email. Then in the morning, I run the upgrade. Hey, I can get all of at once. W.D. it's your cron job I'm looking, so I'll talk about it. It would work, probably most of the time. Your example has both portsdb -Uu and make index in it. Just use one, otherwise your building INDEX-5 twice. Running pkgdb -fu (by the way, make that -uf instead, I know it doesn't make any difference but I look at it and laugh too hard to think about anything else) won't do the trick in the case were you've deleted something and the now missing dependencies were not taken care of. You're going to have to do pkgdb -fF and manually remove the bad dependencies. The one place where I definitely remember this happening was the upgrade from kde32 to kde33. It's easy for someone to shoot down an idea, it's harder to come up with the idea in the first place. Don -- Donald J. O'Neill [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
At 23:11 9/24/2004, Donald J. O'Neill wrote: On Friday 24 September 2004 06:32 pm, Chris wrote: W. D. wrote: At 14:44 9/23/2004, Chris, wrote: You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.htm l An excellent tutorial/article by Dru Lavigne Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. -- Best regards, Chris OK, how about adding a cron job by root like this? (Line will wrap. Everything between '===' on one line) == 15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org /usr/share/examples/cvsup/ports-supfile portsdb -Uu pkgdb -fu cd /usr/ports make index == Then in the morning running: portversion -l Would this automate things without causing problems? Any other safe ways to automate the process? I tend to do this in a periodic cron. Under /etc/periodic/weekly. That also includes the output of portversion to the email. Then in the morning, I run the upgrade. Hey, I can get all of at once. W.D. it's your cron job I'm looking, so I'll talk about it. It would work, probably most of the time. Your example has both portsdb -Uu and make index in it. Just use one, otherwise you're building INDEX-5 twice. Running pkgdb -fu (by the way, make that -uf instead, I know it doesn't make any difference but I look at it and laugh too hard to think about anything else) Yeah, I guess we really want to un-eff the database, rather than eff-up the database. ;^) won't do the trick in the case were you've deleted something and the now missing dependencies were not taken care of. How would one know when this has occurred? You're going to have to do pkgdb -fF and manually remove the bad dependencies. I am clueless here. How would one do this if/when it would happen. The one place where I definitely remember this happening was the upgrade from kde32 to kde33. It's easy for someone to shoot down an idea, it's harder to come up with the idea in the first place. So, are you saying that I should just do this in the cron job: (Line will wrap. Everything between '===' is on one line) == 15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org /usr/share/examples/cvsup/ports-supfile pkgdb -uf cd /usr/ports make index == and then do this manually in the morning: portversion -l and if necessary: portupgrade -arR Start Here to Find It Fast! - http://www.US-Webmasters.com/best-start-page/ $8.77 Domain Names - http://domains.us-webmasters.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
There might be something to be said for doing it my way, after all, Frank Sinatra made a fortune in that manner... /tongue'n'cheek You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne /only slightly-less-tongue-in-cheek ;-) Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
Curtis Vaughan wrote: There might be something to be said for doing it my way, after all, Frank Sinatra made a fortune in that manner... /tongue'n'cheek You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne /only slightly-less-tongue-in-cheek ;-) Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. -- Best regards, Chris King Arthur ran the first knight club. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
On Thursday 23 September 2004 02:44 pm, Chris wrote: Curtis Vaughan wrote: There might be something to be said for doing it my way, after all, Frank Sinatra made a fortune in that manner... /tongue'n'cheek You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne /only slightly-less-tongue-in-cheek ;-) Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. OK Curtis, What the heck are you doing, we just discussed this, Chris, I know better than this and so do you. You guys are supposed to be doing it my way. I think you're just trying to get in good graces with the list so you show up here instead of getting filtered into the bit bucket. Don -- Donald J. O'Neill [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
Donald J. O'Neill wrote: On Thursday 23 September 2004 02:44 pm, Chris wrote: Curtis Vaughan wrote: There might be something to be said for doing it my way, after all, Frank Sinatra made a fortune in that manner... /tongue'n'cheek You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne /only slightly-less-tongue-in-cheek ;-) Kevin Kinsey OK, after reading this tutorial, here is MY new WAY. /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile portsdb -Uu portversion -l[to see if any ports will be upgraded] portupgrade -arR [so dependencies will be installed, if necessary] [NB. If ever asked to run pkgdb -F, do it] Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. OK Curtis, What the heck are you doing, we just discussed this, Chris, I know better than this and so do you. You guys are supposed to be doing it my way. I think you're just trying to get in good graces with the list so you show up here instead of getting filtered into the bit bucket. Don Hahahahaha - No friggin' comment! Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
Hi all, It seems like the message below doesn't belong on this list unless I completely misunderstood the purpose of it. If I'm wrong please let me know. Cheers snipped Taking into consideration other issues or options pointed out on the web tutorial, will this be a good strategy from now on for performing good port upgrades? Curtis Yes - this is more or less how I do mine. OK Curtis, What the heck are you doing, we just discussed this, Chris, I know better than this and so do you. You guys are supposed to be doing it my way. I think you're just trying to get in good graces with the list so you show up here instead of getting filtered into the bit bucket. snipped ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Port upgrading - my way
I got a lot of feedback earlier about ways to do port upgrades and I really appreciate it. I know everyone has their own way. For now, I am doing it the following way. I just want to know whether there is any reason I shouldn't be doing it this way. In other words, by doing it this way is there a potential problem or error that my result? First I run: /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile My ports-supfile reads: *default host=cvsup10.us.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all tag=. Then I run: portupgrade -a That's it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
On Tuesday 21 September 2004 12:40, Curtis Vaughan wrote: Then I run: portupgrade -a That's it. You missed the most important middle step: less /usr/ports/UPDATING to see what critical changes have been made in the meantime that will affect your system. For example, the www/apache2 port recently disabled the various mod_proxy modules by default. Since my company's site depends on those, I would have been in a mess if I hadn't planned to handle that change before running the portupgrade. -- Kirk Strauser pgpEAtXOSkkil.pgp Description: PGP signature
Re: Port upgrading - my way
OK, I took Donald on with his test and this is what I got: Here's my INDEX-5 info before running portversion 4947853 Mar 15 2004 INDEX-5 and here it is after 5804696 Sep 21 13:54 INDEX-5 So, a definite change. And when I ran portversion -vL= the first time, I got the info provided immediately below. But the second time I ran portversion -vL= there was not output. So, what exactly does that mean? and does that mean that now I should run portupgrade -a now? apache-1.3.31_6 succeeds port (port has 1.3.29_3) bandwidthd-1.2.1 succeeds port (port has 1.2.0_1) bash-2.05b.007_2 succeeds port (port has 2.05b.007) bsdiff-4.2succeeds port (port has 4.1) expat-1.95.8 succeeds port (port has 1.95.7) ezm3-1.2 succeeds port (port has 1.1_1) freebsd-update-1.6succeeds port (port has 1.5) freetype2-2.1.7_3 succeeds port (port has 2.1.5_2) gd-2.0.25,1 succeeds port (port has 2.0.15_1,1) jpeg-6b_3 succeeds port (port has 6b_1) libiconv-1.9.2_1 succeeds port (port has 1.9.1_3) libtool-1.5.8 succeeds port (port has 1.5.2_1) m4-1.4.1 succeeds port (port has 1.4_1) openldap-client-2.2.15succeeds port (port has 2.2.6) p5-Net-SSLeay-1.25succeeds port (port has 1.23) pam_ldap-1.7.1_1 succeeds port (port has 1.6.7_1) perl-5.8.5succeeds port (port has 5.8.2_5) png-1.2.6 succeeds port (port has 1.2.5_3) popt-1.7 succeeds port (port has 1.6.4_2) portupgrade-20040701_3succeeds port (port has 20040208) postfix-2.1.4,1 succeeds port (port has 2.0.18,1) rsync-2.6.2_3 succeeds port (port has 2.6.0) ruby-1.8.2.p2_1 succeeds port (port has 1.8.1_2) samba-2.2.11_1succeeds port (port has 2.2.8a_1) sudo-1.6.8.1 succeeds port (port has 1.6.7.5) unzip-5.51succeeds port (port has 5.50_2) webmin-1.150_5succeeds port (port has 1.130_10) On 21 Sep, 2004, at 12:22, Donald J. O'Neill wrote: On Tuesday 21 September 2004 12:40 pm, Curtis Vaughan wrote: I just want to know whether there is any reason I shouldn't be doing it this way. In other words, by doing it this way is there a potential problem or error that my result? Yes, there is. As far as I can tell from what you've given, you're depending on INDEX-5 to be up to date after your ports upgrade. I don't believe it is and you need to run make index or some other means of getting INDEX-5 to be up to date.. Try this experiment: cvsup your ports note the date and size of /usr/ports/INDEX-5 run portversion -vL= or portversion -rRvc keep track of that output now cd /usr/ports make index note the date and size of INDEX-4 run portversion -vL= or portverstion -rRvc I think you'll see a lot more of your installed stuff needs updating. Don -- Donald J. O'Neill [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port upgrading - my way
Curtis Vaughan wrote: OK, I took Donald on with his test and this is what I got: Here's my INDEX-5 info before running portversion 4947853 Mar 15 2004 INDEX-5 and here it is after 5804696 Sep 21 13:54 INDEX-5 So, a definite change. There might be something to be said for doing it my way, after all, Frank Sinatra made a fortune in that manner... /tongue'n'cheek You could join in the FreeBSD tradition, though, and do it the Right Way(tm) ... http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.html An excellent tutorial/article by Dru Lavigne /only slightly-less-tongue-in-cheek ;-) Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
