Context Navigation

Changes between Initial Version and Version 1 of Ticket #50000, comment 16

initial	v1
7	7	This could also be a specific port; that would allow the perl port devs to push tested versions of the updating script, when they're ready, either through an upgrade of that port, or through an independent download.
8	8
9		In light with those last thoughts: selective updating would probably be easier if all perl portdirs were moved into a dedicated subdirectory so one could do something like `(cd ~~`port dir perl5`~~/.. ; svn up)`.
	9	In light with those last thoughts: selective updating would probably be easier if all perl portdirs were moved into a dedicated subdirectory so one could do something like `(cd $(port dir perl5)/.. ; svn up)`.
10	10
11	11	Another approach I'm testing with my own KF5 ports: specify the current version (and possibly a "latest" version) in the PortGroup which all ports providing perl-related things are supposed to include anyway (unless that messes up the configure.cmd, build.cmd etc, like the Python PortGroup does?). It seems to work, though I have occasional ports that don't pick up a version upgrade after running portindex.