> tag 356983 upstream > thanks > > > 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:
Right. It only becomes useful when your SM installation becomes out of date. (Although, as I mention, it *COULD* be useful right away if a plugin requires some functionality only included in DEVEL.) > 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. Right. So you could make the argument that the plugin should just be downloaded separately as it is today, but I think the advantage of including it in the distro and offering updated "library" downloads is that it becomes an official SM team thing -- we can all pitch in to make its library more useful. It also means that it won't need a patch any more, which would be nice. > 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. It could, but it seems much more appropriate to offer it separately. > > 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. It's already been brought up twice, so I feel as though I have the go-ahead already... now I just need to find some time for it. ;) Cheers, Paul
