On 18/02/2014 4:51 PM, Doug Hardie wrote:

On 17 February 2014, at 21:43, Erich Dollansky <[email protected]> 
wrote:

Hi,

On Mon, 17 Feb 2014 21:07:43 -0800
Doug Hardie <[email protected]> wrote:

I have an older, but basically clean, install of 8.2 on a production
system.  It has a few ports that were installed back when 8.2 was
new.  However, I need to add pdftk.  Pkg_add did that nicely.
HOwever, it added version 1.44.  The history for pdftk shows that a
major problem was fixed in 1.45 and I am encountering that problem
and need to upgrade.  Portupgrade pdftk does nothing.  It seems to
decide that the latest version is 1.44.  However, on a 9.2 system, I
get a much higher version number.  Is there any way to determine if
1.44 is the latest version that will run with 8.2 or is there another
way I need to upgrade to ports files?  Its my understanding that
cvsup is no longer with us.

how I understand your problem, the behaviour of the machine is normal
as you kept the old ports tree.

If you would like to have a newer version of a port, you would have to
update the ports tree first. The big but is then that you will have to
update all installed ports too and then install the program you need.

If you have real bad luck, this could force you even to upgrade from
8.2 to 8.4. So, be careful.

Thats what I expected, but the question remains:  how?  Cvsup I believe is no 
longer with us and purtupgrade apparently doesn't do that either.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"


with portsnap:

# portsnap fetch extract
# portsnap update


with subversion:

# cd /usr/ports/devel/subversion && make install clean
# svn checkout https://svn0.eu.FreeBSD.org/ports/head /usr/ports
# svn update /usr/ports

--
bsdbox.co
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[email protected]"

Reply via email to