On Sat, Aug 04, 2007 at 07:55:06AM -0400, Dan Mahoney, System Admin wrote: > No, but YOU (the SA team) can, in fact, list all of the modules that you > are shipping with a specific version of SA, in a commented (and possibly > commented out) version of $version.pre.
Sure, and that's exactly what we already do. It's just that $version is the
version the plugin was first introduced.
> would be nice things too (as presumably, nothing is going to ever REMOVE
> that old module from its installed location for those of us using the
> make, make install method, and because SA will still read the
> three-versions-ago command to LOAD that module.
Yeah, it's hard to remove the old plugins, though we could overwrite them with
a new version that has all the code ripped out. It could even raise a flag
saying that the plugin is deprecated.
> Even now, there could be functionality I'm missing, simply because I
> haven't installed every minor version in between.
If you were to upgrade from say 3.0.3 to 3.2.0, the install process will
install all of the v31x.pre files, and the plugins in 3.2.0 are inclusive of
all the ones from 3.1.x. So you're not missing anything if you didn't
install all the ones in between.
--
Randomly Selected Tagline:
"When we traded it in my wife was upset because we didn't keep it long
enough for her to buy a gun and shoot it."
- Unknown about the Cadillac Cimarron
pgpKeo9x0cYHd.pgp
Description: PGP signature
