Re: upgrading installed ports: time to do it ?
On Wednesday 24 June 2009 17:19:09 you wrote:
> On Monday, 22 June 2009 16:48:02 RW wrote:
> > On Mon, 22 Jun 2009 20:58:41 +0100
> >
> > Chris Whitehouse wrote:
> > > I'll probably get flamed for this but since I've been using
> > > ports-mgmt/portmanager I've almost forgotten
> > > about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it
> > > was. I've upgraded ports just by doing 'portmanager -u' over one or
> > > two quite major changes and not had any problems that haven't been
> > > down to an individual ports.
> >
> > You still need to read UPDATING, portmanager handles some of the
> > issues automatically, but not all.
> > ___
> > 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"
>
> Hello,
>
> Here is a perl hack I use to automatically read and parse UPDATING as part
> of my daily upgrade routine. It is part of a larger set of five scripts
> which use:
> 1. "csup" to update ports
> 2. "make index" to update the /usr/ports/INDEX
> 3. "pkg_version" to identify the ports that need upgrading
> 4. "portfetch" to download the tarballs
> 5. a script to display the relevant contents, if any, of UPDATING using
> the hack shown below and the contents identified in step 3 above.
>
> These five scripts are combined in a master script (csup-all) which I
> invoke the first thing in the morning. After doing some other morning
> chores I then run "portconfig -a -v" to set up any configuration settings
> prior to running "portmaster -a -u". Everything is automatic except for
> the configuration.
>
> Here is the perl hack. It can be improved by comparing the ports that need
> to be updated (step 3) with the ports specified within UPDATING (step 5).
> The embedded ansi codes will work with the default FreeBSD console
> settings, otherwise they can be removed.
>
> #!/usr/bin/perl
> #
> # file:csup-update.pl
> #
> # created: 2006-07-16
> #
> # purpose: To review update notes in /usr/ports/UPDATING
> # This program will only display those notes issued
> # since last csup
> #
> # algorithm: Each line of the file /usr/ports/UPDATING is scanned and if
> # it finds a date in the form ^mmdd$ the date is assigned
> # to the variable $date. Otherwise all non-date lines are printed
> # to STDOUT. As soon as this program finds a date older than the
> # last update this program quits and prints an appropriate closing
> # message.
> #
> unless ( open ( MYFILE, "/usr/ports/UPDATING" ) ) {
> die ("Cannot open input file /usr/ports/UPDATING.\n") ;
> }
>
> unless ( open ( LASTUPDATE, "/root/bin/csup-lastupdate.txt" ) ) {
> die ("Cannot open file csup-lastupdate.txt.\n") ;
> }
>
> $eof = '' ;
> $date = $lastupdate = ;
> $line = ;
> $count = 0 ;
>
> while ( $line ne $eof ) {
> if ( $line =~ /^2\d{7}/ ) {
> $date = $line ;
> $date =~ tr/://d ;
> $count++ ;
> }
>
> if ( ( $date - $lastupdate ) >= 0 ) {
> if ( $line =~ /^2\d{7}/ ) {
> print ("^[[32m$line^[[0m") ;
> } else {
> print ("^[[0m$line") ;
> }
> $line = ;
> $date = $lastupdate ;
> } else {
> $count-- ;
> if ( $count == 0 ) {
> print ( "^[[36mThere are no updates to review. ") ;
> } elsif ( $count == 1 ) {
> print ( "^[[36mThere is only one update to review. ") ;
> } else {
> print ( "^[[36mThere are $count updates to review. ") ;
> }
> chop ( $lastupdate ) ;
> print ( "The last run of csup was on $lastupdate.^[[0m\n\n" ) ;
>
> exit ;
> }
> }
> # EoF
>
> ___
> 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"
Hello mfv !
Thanks for sharing your perl hack and your experience :-)
I do not know anything about PERL, but I am starting taking a look at this !
THanks
dan
___
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: upgrading installed ports: time to do it ?
On Thu, 25 Jun 2009 20:20:12 +0100 Chris Whitehouse wrote: > RW wrote: > > Portmanger does cope with most of the "portupgrade -o" and > > "portupgrade -r" entries, although sometime it will need to be run > > (or rerun) in pristine-mode. > > just curious, do you know this because you know how they all work or > have you tried them. And how does portmaster fit in? Does it use the > same 'leaf-nodes first' algorithm as portmanager? It's leaf-last, the leaves are on the top of the tree. All the upgrade tools build in dependency order, but portmanager also rebuilds ports that directly depend on the ports it's upgraded (originally it included indirect dependencies, but that's now only done in pristine mode). In other words it, more or less, does the equivalent of "portupgrade -fr" as a matter of course. As regards "portupgrade -o", it depends on the circumstances. In the case of perl5.8 to perl5.10, I would expect that it would continue with perl5.8 until something actually needs perl5.10. It would then detect a conflict, remove perl5.8, install perl5.10 and then rebuild everything that depended on perl5.8. Essentially it would do the right thing. I'm not sure about python, it's bit more complicated, but I would guess it would be similar to perl. ___ 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: upgrading installed ports: time to do it ?
RW wrote: On Tue, 23 Jun 2009 22:21:21 +0100 Chris Whitehouse wrote: RW wrote: On Mon, 22 Jun 2009 20:58:41 +0100 Chris Whitehouse wrote: I'll probably get flamed for this but since I've been using ports-mgmt/portmanager I've almost forgotten about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it was. I've upgraded ports just by doing 'portmanager -u' over one or two quite major changes and not had any problems that haven't been down to an individual ports. You still need to read UPDATING, portmanager handles some of the issues automatically, but not all. Not trolling but can you give me some examples? Many of of the entries aren't solely to do with guiding portmaster/portupgrade through the upgrade, they may also involve migrating configuration or user data, or performing other administrative tasks. Portmanger does cope with most of the "portupgrade -o" and "portupgrade -r" entries, although sometime it will need to be run (or rerun) in pristine-mode. just curious, do you know this because you know how they all work or have you tried them. And how does portmaster fit in? Does it use the same 'leaf-nodes first' algorithm as portmanager? However, it doesn't always work correctly when software has been repackaged because this can create temporary unrecorded conflicts which are difficult for any tool to deal with. If you see any instructions to remove packages before upgrading, it's prudent to follow them. Thanks, I'll pay more attention. Maybe I got lucky in the past. Chris ___ 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" ___ 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: upgrading installed ports: time to do it ?
dan wrote: On Tuesday 23 June 2009 23:21:21 Chris Whitehouse wrote: RW wrote: On Mon, 22 Jun 2009 20:58:41 +0100 Chris Whitehouse wrote: I'll probably get flamed for this but since I've been using ports-mgmt/portmanager I've almost forgotten about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it was. I've upgraded ports just by doing 'portmanager -u' over one or two quite major changes and not had any problems that haven't been down to an individual ports. You still need to read UPDATING, portmanager handles some of the issues automatically, but not all. Not trolling but can you give me some examples? Chris ___ 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" Yes. I think there is at least one. Please, consider to correct me if I am wrong. Yesterday, reading the contents of /usr/src/UPDATING in the source tree (using portupdate-scan) I found : "[...] 20090608: AFFECTS: users of lang/python* and py-* AUTHOR: m...@freebsd.org The default version of Python has been changed from 2.5.x to 2.6.x. If you have 2.5.x installed, perform an upgrade of lang/python25 to lang/python26 with the following command: [...] " Can portmanager know that the default version of a port has been changed and then you need to do the upgrade to the newer major version ? I don't know. I will put testing it on my todo list (which I really do hope to get around to :) Chris And if it can know that... can also portmanager know that "[...] Once the installed Python has been updated to 2.6, by using the method above, it is required to run the upgrade-site-packages target in lang/python to assure that site-packages are made available to the new Python version. [...] "? If, otherwise, using portmanager you end up with a newer version of python 2.5 (for example)... are you sure that every upgrade in the future will work flawlessly ? After Reading the UPDATING file a guy will " [...] set the PYTHON_DEFAULT_VERSION variable to 'python2.5' without quotes in make.conf, then go to lang/python and perform the following command: [...] " will portmanager do the same ? d ___ 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" ___ 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: upgrading installed ports: time to do it ?
On Monday, 22 June 2009 16:48:02 RW wrote:
> On Mon, 22 Jun 2009 20:58:41 +0100
>
> Chris Whitehouse wrote:
> > I'll probably get flamed for this but since I've been using
> > ports-mgmt/portmanager I've almost forgotten
> > about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it
> > was. I've upgraded ports just by doing 'portmanager -u' over one or
> > two quite major changes and not had any problems that haven't been
> > down to an individual ports.
>
> You still need to read UPDATING, portmanager handles some of the
> issues automatically, but not all.
> ___
> 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"
Hello,
Here is a perl hack I use to automatically read and parse UPDATING as part of
my daily upgrade routine. It is part of a larger set of five scripts which
use:
1. "csup" to update ports
2. "make index" to update the /usr/ports/INDEX
3. "pkg_version" to identify the ports that need upgrading
4. "portfetch" to download the tarballs
5. a script to display the relevant contents, if any, of UPDATING using the
hack shown below and the contents identified in step 3 above.
These five scripts are combined in a master script (csup-all) which I invoke
the first thing in the morning. After doing some other morning chores I then
run "portconfig -a -v" to set up any configuration settings prior to running
"portmaster -a -u". Everything is automatic except for the configuration.
Here is the perl hack. It can be improved by comparing the ports that need to
be updated (step 3) with the ports specified within UPDATING (step 5). The
embedded ansi codes will work with the default FreeBSD console settings,
otherwise they can be removed.
#!/usr/bin/perl
#
# file:csup-update.pl
#
# created: 2006-07-16
#
# purpose: To review update notes in /usr/ports/UPDATING
# This program will only display those notes issued
# since last csup
#
# algorithm: Each line of the file /usr/ports/UPDATING is scanned and if
# it finds a date in the form ^mmdd$ the date is assigned
# to the variable $date. Otherwise all non-date lines are printed
# to STDOUT. As soon as this program finds a date older than the
# last update this program quits and prints an appropriate closing
# message.
#
unless ( open ( MYFILE, "/usr/ports/UPDATING" ) ) {
die ("Cannot open input file /usr/ports/UPDATING.\n") ;
}
unless ( open ( LASTUPDATE, "/root/bin/csup-lastupdate.txt" ) ) {
die ("Cannot open file csup-lastupdate.txt.\n") ;
}
$eof = '' ;
$date = $lastupdate = ;
$line = ;
$count = 0 ;
while ( $line ne $eof ) {
if ( $line =~ /^2\d{7}/ ) {
$date = $line ;
$date =~ tr/://d ;
$count++ ;
}
if ( ( $date - $lastupdate ) >= 0 ) {
if ( $line =~ /^2\d{7}/ ) {
print ("^[[32m$line^[[0m") ;
} else {
print ("^[[0m$line") ;
}
$line = ;
$date = $lastupdate ;
} else {
$count-- ;
if ( $count == 0 ) {
print ( "^[[36mThere are no updates to review. ") ;
} elsif ( $count == 1 ) {
print ( "^[[36mThere is only one update to review. ") ;
} else {
print ( "^[[36mThere are $count updates to review. ") ;
}
chop ( $lastupdate ) ;
print ( "The last run of csup was on $lastupdate.^[[0m\n\n" ) ;
exit ;
}
}
# EoF
___
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: upgrading installed ports: time to do it ?
On Tue, 23 Jun 2009 22:21:21 +0100 Chris Whitehouse wrote: > RW wrote: > > On Mon, 22 Jun 2009 20:58:41 +0100 > > Chris Whitehouse wrote: > > > >> I'll probably get flamed for this but since I've been using > >> ports-mgmt/portmanager I've almost forgotten > >> about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever > >> it was. I've upgraded ports just by doing 'portmanager -u' over > >> one or two quite major changes and not had any problems that > >> haven't been down to an individual ports. > > > > You still need to read UPDATING, portmanager handles some of the > > issues automatically, but not all. > > Not trolling but can you give me some examples? Many of of the entries aren't solely to do with guiding portmaster/portupgrade through the upgrade, they may also involve migrating configuration or user data, or performing other administrative tasks. Portmanger does cope with most of the "portupgrade -o" and "portupgrade -r" entries, although sometime it will need to be run (or rerun) in pristine-mode. However, it doesn't always work correctly when software has been repackaged because this can create temporary unrecorded conflicts which are difficult for any tool to deal with. If you see any instructions to remove packages before upgrading, it's prudent to follow them. ___ 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: upgrading installed ports: time to do it ?
On Tuesday 23 June 2009 23:21:21 Chris Whitehouse wrote: > RW wrote: > > On Mon, 22 Jun 2009 20:58:41 +0100 > > > > Chris Whitehouse wrote: > >> I'll probably get flamed for this but since I've been using > >> ports-mgmt/portmanager I've almost forgotten > >> about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it > >> was. I've upgraded ports just by doing 'portmanager -u' over one or > >> two quite major changes and not had any problems that haven't been > >> down to an individual ports. > > > > You still need to read UPDATING, portmanager handles some of the > > issues automatically, but not all. > > Not trolling but can you give me some examples? > > Chris > ___ > 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" Yes. I think there is at least one. Please, consider to correct me if I am wrong. Yesterday, reading the contents of /usr/src/UPDATING in the source tree (using portupdate-scan) I found : "[...] 20090608: AFFECTS: users of lang/python* and py-* AUTHOR: m...@freebsd.org The default version of Python has been changed from 2.5.x to 2.6.x. If you have 2.5.x installed, perform an upgrade of lang/python25 to lang/python26 with the following command: [...] " Can portmanager know that the default version of a port has been changed and then you need to do the upgrade to the newer major version ? And if it can know that... can also portmanager know that "[...] Once the installed Python has been updated to 2.6, by using the method above, it is required to run the upgrade-site-packages target in lang/python to assure that site-packages are made available to the new Python version. [...] "? If, otherwise, using portmanager you end up with a newer version of python 2.5 (for example)... are you sure that every upgrade in the future will work flawlessly ? After Reading the UPDATING file a guy will " [...] set the PYTHON_DEFAULT_VERSION variable to 'python2.5' without quotes in make.conf, then go to lang/python and perform the following command: [...] " will portmanager do the same ? d ___ 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: upgrading installed ports: time to do it ?
Jerry wrote: On Mon, 22 Jun 2009 20:58:41 +0100 Chris Whitehouse wrote: I'll probably get flamed for this but since I've been using ports-mgmt/portmanager I've almost forgotten about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it was. I've upgraded ports just by doing 'portmanager -u' over one or two quite major changes and not had any problems that haven't been down to an individual ports. I've never seen any reasons given for not using portmanager, just it seems to be getting quietly deprecated, which is a shame because it works supremely well. Having said that why not check out http://freebsd-custom.wikidot.com/, the new binary ports upgrade system and save yourself a bunch of compile time. Chris I use it myself, It "just works". I would also add "-p -l" to the command line. that way you have a log created if something does go wrong. It will also fix up any outdated dependencies. I do use logging. In fact I do 'portmanager -s > somefile', extract a list of ports to be upgraded and run the list through a loop which does 'make config' for each port, _then_ run 'portmanager -l -u' so it runs completely unattended. It does indeed "just works" which is down to the way it works out to do leaf ports first and work backwards. portmaster looks like it has some nice features, including doing all the configs first, but I don't know if it does as good a job as portmanager in deciding what order to do things. Chris ___ 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: upgrading installed ports: time to do it ?
RW wrote: On Mon, 22 Jun 2009 20:58:41 +0100 Chris Whitehouse wrote: I'll probably get flamed for this but since I've been using ports-mgmt/portmanager I've almost forgotten about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it was. I've upgraded ports just by doing 'portmanager -u' over one or two quite major changes and not had any problems that haven't been down to an individual ports. You still need to read UPDATING, portmanager handles some of the issues automatically, but not all. Not trolling but can you give me some examples? Chris ___ 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: upgrading installed ports: time to do it ?
On Mon 22 Jun 2009 at 13:48:02 PDT RW wrote: On Mon, 22 Jun 2009 20:58:41 +0100 Chris Whitehouse wrote: I'll probably get flamed for this but since I've been using ports-mgmt/portmanager I've almost forgotten about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it was. I've upgraded ports just by doing 'portmanager -u' over one or two quite major changes and not had any problems that haven't been down to an individual ports. You still need to read UPDATING, portmanager handles some of the issues automatically, but not all. that durned human element again! would be nice if a port upgrade tool did that for you, displayed any entries related to ports that need updating, and gave you a chance to postpone the update until you've taken whatever actions UPDATING suggests would require UPDATING to be written in a consistent, machine-readable format ___ 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: upgrading installed ports: time to do it ?
On Mon, 22 Jun 2009 20:58:41 +0100 Chris Whitehouse wrote: > I'll probably get flamed for this but since I've been using > ports-mgmt/portmanager I've almost forgotten > about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it > was. I've upgraded ports just by doing 'portmanager -u' over one or > two quite major changes and not had any problems that haven't been > down to an individual ports. You still need to read UPDATING, portmanager handles some of the issues automatically, but not all. ___ 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: upgrading installed ports: time to do it ?
On Mon, 22 Jun 2009 20:58:41 +0100 Chris Whitehouse wrote: > I'll probably get flamed for this but since I've been using > ports-mgmt/portmanager I've almost forgotten > about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it > was. I've upgraded ports just by doing 'portmanager -u' over one or > two quite major changes and not had any problems that haven't been > down to an individual ports. > > I've never seen any reasons given for not using portmanager, just it > seems to be getting quietly deprecated, which is a shame because it > works supremely well. > > Having said that why not check out > http://freebsd-custom.wikidot.com/, the new binary ports upgrade > system and save yourself a bunch of compile time. > > Chris I use it myself, It "just works". I would also add "-p -l" to the command line. that way you have a log created if something does go wrong. It will also fix up any outdated dependencies. -- Jerry ges...@yahoo.com Genealogy, n.: An account of one's descent from an ancestor who did not particularly care to trace his own. -- Ambrose Bierce, "The Devil's Dictionary" ___ 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: upgrading installed ports: time to do it ?
Chris Rees wrote: 2009/6/21 danny : Hi list members , I frequently update the contents of the ports tree but I have never upgraded any port. I am studying the way to do it, by following the handbook and an article on The FreeBSD Diary about the use of portupgrade. At the moment I am focuing the attention to the '/usr/ports/UPDATING' file. The question that arose is the following: is there any automated way to check if any of the port to be upgraded has specific upgrading notes written in that file ? Do you prefer doing a mass or selective upgrade ? Thanks ! dan I'll probably get flamed for this but since I've been using ports-mgmt/portmanager I've almost forgotten about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it was. I've upgraded ports just by doing 'portmanager -u' over one or two quite major changes and not had any problems that haven't been down to an individual ports. I've never seen any reasons given for not using portmanager, just it seems to be getting quietly deprecated, which is a shame because it works supremely well. Having said that why not check out http://freebsd-custom.wikidot.com/, the new binary ports upgrade system and save yourself a bunch of compile time. Chris ___ 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: upgrading installed ports: time to do it ?
On Sunday 21 June 2009 10:38:39 danny wrote: > At the moment I am focuing the attention to the '/usr/ports/UPDATING' file. > The question that arose is the following: is there any automated way to > check if any of the port to be upgraded has specific upgrading notes > written in that file ? /usr/sbin/pkg_updating, but it's flaky since /usr/ports/UPDATING is human written. It's a school example of a file that should really be XML: human readable/writeable and machine parseable, but it's not. So we end up with entries like: AFFECTS: users of Japanese and Chinese fonts AFFECTS: users of linux Fedora 8 infrastructure ports AFFECTS: users of Tcl/Tk which cannot ever be translated to ports by a machine. -- Mel ___ 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: upgrading installed ports: time to do it ?
On Sun, Jun 21, 2009 at 09:07:51PM +0100, Chris Rees wrote: > 2009/6/21 danny : > > I frequently update the contents of the ports tree but I have never upgraded > > any port. I am studying the way to do it, by following the handbook and an > > article on The FreeBSD Diary about the use of portupgrade. > > At the moment I am focuing the attention to the '/usr/ports/UPDATING' file. > > The question that arose is the following: is there any automated way to > > check > > if any of the port to be upgraded has specific upgrading notes written in > > that file ? Try ports-mgmt/portupdate-scan. It attempts to filter UPDATING to only show entries pertinent to your installed ports. Alex ___ 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: upgrading installed ports: time to do it ?
2009/6/21 danny : > Hi list members , > > I frequently update the contents of the ports tree but I have never upgraded > any port. I am studying the way to do it, by following the handbook and an > article on The FreeBSD Diary about the use of portupgrade. > At the moment I am focuing the attention to the '/usr/ports/UPDATING' file. > The question that arose is the following: is there any automated way to check > if any of the port to be upgraded has specific upgrading notes written in > that file ? > Do you prefer doing a mass or selective upgrade ? > > Thanks ! > > dan I would tend to upgrade perl first; have a look in UPDATING to see how it's done. That'll upgrade the majority of your ports too. You may also have a small problem if you're still running XFree86 (which you probably will if you've had your system a while). Look in UPDATING for that too, and then just do a portupgrade -aP. Good luck, and I hope your processor's properly cooled! Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? ___ 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"
