Re: Upgrading Ports on 5.3
Chris Hill wrote: On Sun, 11 Jun 2006, Ron wrote: Is there a way to use the current ports system if I am still running 5.3? That's the only way. I really need to update subversion, mysql, plus make sure I'm running the latest versions of other software, but since 5.4 came out (and now 5.5 and 6.0), I am no longer been able to get new ports. If change my cvs-supfile to be: -- *default tag=RELENG_5_4 I second what Bill Moran said: "tag=." for ports. I keep two separate supfiles - one for the system, another for ports. (I'm also running 5.4 on this machine.) I'll send them to you off-list if you want. If you still have the original ports tree from when you installed 5.4, it's kind of long in the tooth by now and there may initially be a certain amount of dependency hell, but I'd bite the bullet and do it anyway when you have a free Saturday; it will fix a lot of problems, and will be less trouble down the road. If someone can point me to some specific information that will help, I would be very appreciative. What I usually do is # cvsup -g /etc/cvsupfile.ports <- my ports supfile with "tag=." I've found the very excellent portmanager walks through most complex updates. It will only upgrade ports that need it but if yours are old that probably means most so it's going to take time. portmanager -s will tell you what needs to be done portmanager -u -l will do it. If you are upgrading jdk14 run make -n in the java/jdk14 directory and manually fetch any files it wants into distfiles/. Also I run portmanager -s > some.file to get a list of what needs doing, then use some.file to make a script that looks in each port directory that's going to get upgraded and does make config - then portmanager can pretty well run unattended. (I'm still experimenting with the make config bit so ymmv) Chris # pkgdb -aF <- may throw a lot of errors, esp. <- if you have an old ports tree. <- Fix manually if needed! # cd /usr/ports # portsdb -u # portsclean -C # pkgdb -u # portversion -v | grep needs <- see what "needs" to be upgraded ...and then # portupgrade -Rr or if I really have a lot of time, # portupgrade -aRr ...which will upgrade everything, but may take many hours even on a fast machine. HTH. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging <|> ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading Ports on 5.3
RW wrote: On Wednesday 14 June 2006 11:12, Alex Zbyslaw wrote: [portversion -L =] would be quicker. Any > needs upgrading. Any < would mean you somehow had an installed version newer that the port version! Presumably that could happen if the port were reverted. For completeness, looks like I got it backwards: < The installed version of the package is older than the current version. > The installed version of the package is newer than the current version. This situation can arise with using an out-of-date INDEX file, or when testing new ports. And yes, a reverted port would do it too, I expect. And my system shows tons of > (which is what confused me) whereas pkg_version shows lots of =. Looks like you have to be religious about keeping INDEX up to date. pkg_version -L = is functionally equivalent, slower, but doesn't require up-to-date INDEX (which just takes too long to build and I usually forget or can't be bothered). portversion -> tidy completists pkg_version -> lazy sods like me --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading Ports on 5.3
On Wednesday 14 June 2006 11:12, Alex Zbyslaw wrote: > would be quicker. Any > needs upgrading. Any < would mean you somehow > had an installed version newer that the port version! Presumably that could happen if the port were reverted. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading Ports on 5.3
Chris Hill wrote: What I usually do is # cvsup -g /etc/cvsupfile.ports <- my ports supfile with "tag=." # pkgdb -aF <- may throw a lot of errors, esp. <- if you have an old ports tree. <- Fix manually if needed! # cd /usr/ports # portsdb -u # portsclean -C # pkgdb -u # portversion -v | grep needs <- see what "needs" to be upgraded # portversion -L = would be quicker. Any > needs upgrading. Any < would mean you somehow had an installed version newer that the port version! # less /usr/ports/UPDATING to see if any of the ports you will upgrade have "issues" --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading Ports on 5.3
On Sun, 11 Jun 2006, Ron wrote: Is there a way to use the current ports system if I am still running 5.3? That's the only way. I really need to update subversion, mysql, plus make sure I'm running the latest versions of other software, but since 5.4 came out (and now 5.5 and 6.0), I am no longer been able to get new ports. If change my cvs-supfile to be: -- *default tag=RELENG_5_4 I second what Bill Moran said: "tag=." for ports. I keep two separate supfiles - one for the system, another for ports. (I'm also running 5.4 on this machine.) I'll send them to you off-list if you want. If you still have the original ports tree from when you installed 5.4, it's kind of long in the tooth by now and there may initially be a certain amount of dependency hell, but I'd bite the bullet and do it anyway when you have a free Saturday; it will fix a lot of problems, and will be less trouble down the road. If someone can point me to some specific information that will help, I would be very appreciative. What I usually do is # cvsup -g /etc/cvsupfile.ports <- my ports supfile with "tag=." # pkgdb -aF <- may throw a lot of errors, esp. <- if you have an old ports tree. <- Fix manually if needed! # cd /usr/ports # portsdb -u # portsclean -C # pkgdb -u # portversion -v | grep needs <- see what "needs" to be upgraded ...and then # portupgrade -Rr or if I really have a lot of time, # portupgrade -aRr ...which will upgrade everything, but may take many hours even on a fast machine. HTH. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging <|> ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading Ports on 5.3
Ron <[EMAIL PROTECTED]> wrote: > Is there a way to use the current ports system if I am still running 5.3? > > I really need to update subversion, mysql, plus make sure I'm running the > latest versions of other software, but since 5.4 came out (and now 5.5 and > 6.0), I am no longer been able to get new ports. > > If change my cvs-supfile to be: > > -- > *default tag=RELENG_5_4 Use "tag=." when fetching ports. -- Bill Moran That seem right to you? Jubal Early ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
