tag 356983 upstream thanks Hello Paul,
> Eons ago, Erin and I had a discussion where we decided that > Compatibility *should* be included as a plugin in the standard distro. > That was before it required a patch, but I think I am still going to > run with it in the near future. Ok. Since this is something that can be put on the agenda within the SquirrelMail project, I'll flag this as 'upstream' in Debian: we'll follow the upstream decision on that. > You raised the concern that when you get the NEWEST distro, there is > absolutely NO NEED to have the plugin, since everything is up to date > (although there might be things backported from the DEVEL stream that > are not even in the newest STABLE). However, the idea was that we would > keep the compatibility "library" in CVS, available for download as needed, > similar to how Tomas is packaging the locales in CVS, separate from the > core product. My only concern for that scenario is internal -- that the > team won't necessarily keep the library up to date, but that's somewhat > aside from the point.... Ah, that's already something different. The request (and my initial thoughts) was to include it just like we now include the listcommands plugin. I don't think that situation is useful: the plugin comes into play if you're not running the newest version. If you're running an old version and would need that plugin, the packaged plugin is out of date and not useful. The plugin is at its best if it's fresh. Maintaining it in upstream CVS can be a good idea; but this would not have to be a part of the SquirrelMail tarballs we make. > If you'd like to talk it over again on the SM DEVEL list, we can do that. Sure; please bring it up if you think this can improve SquirrelMail. bye, Thijs
