[Seaside-dev] Detecting installed Seaside versions?

Andreas Raab andreas.raab at gmx.de
Wed Nov 25 05:26:41 UTC 2009


Julian Fitzell wrote:
> On Tue, Nov 24, 2009 at 7:42 PM, Colin Putney <cputney at wiresong.ca> wrote:
>> For now I'd bet there *is* check-for-WAFrumbazzle-style algorithm out there,
>> but somebody will have to do the analysis to figure out what it is. It might
>> not be *that* complicated... I bet "SeasidePlatformSupport versionString" is
>> a good place to start. For the alpha versions of 2.9 and 3.0, there's been a
>> lot of package churn, so it shouldn't be hard to figure out what version is
>> present based on that. Before SeasidePlatformSupport existed... well, how
>> far back to you want to go?
> 
> Yes, use "SeasidePlatformSupport versionString" for 2.8.*. I'd say
> don't worry about pre-release versions on 2.9/3.0. And let's make sure
> we have a simple solution in place for 3.0b1.
> 
> http://code.google.com/p/seaside/issues/detail?id=503

Sounds good, I'll do that. I'm trying to support "common" versions of 
Seaside, i.e., versions that are in use today and that someone would 
likely install. I guess that would limit it to 2.8 (possibly variants) 
and 3.0, no?

Cheers,
   - Andreas


More information about the seaside-dev mailing list