Do our version numbers mean nothing? It would seem our own scripts that do break on releases should be smart enough to realize a change in MacPorts version.
On May 20, 2014, at 22:45, Ryan Schmidt <ryandes...@macports.org> wrote: > On May 20, 2014, at 19:56, Jeremy Lavergne wrote: > >> Is this something we should have the scripts check before running? If the >> MacPorts version is newer than they’re expecting, demand the user download a >> fresh copy. > > This seems like overkill to me. Most MacPorts releases haven't made the types > of internal changes that were made in 2.3.0 that cause changes in scripts to > be necessary. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
