[mapserver-dev] Packaging multiple version of mapserver

[Bruno Friedmann]

On lundi, 13 février 2017 11.21:20 h CET Bruno Friedmann wrote:
> Dear devs, since last year tosprint in Paris,
> I was able in a sense to have multiple major version of mapserver build for
> openSUSE (rpm based).
> There's still a number of opened questions, that I would like to resolve
> with dev team, to make a final proposal, and send to packages to
> appropriate repository, where end users can consume them.
> 
> The idea behind this is to allow users to keep their existing working
> installation (think about .map compatibility), and start migrating as soon
> as possible.
> 
> To make it short I've a mapserver6 (based on 6.4x branch) and mapserver7
> (actually 7.0.4).
> This work well for core and main componants.
> For example libmapserver2 (7.0.4)
> rpm -ql libmapserver2
> /usr/lib64/libmapserver.so.2
> /usr/lib64/libmapserver.so.7.0.4
> 
> Users can have both installed on their system, and with update-alternatives
> can choose which one is the default.
> 
> On the mapscript side, it is more complicated as the mapscript component
> doesn't get versionned actually by our build.
> So I let user choosing one or the other depending on their needs.
> Not perfect, but that's all I can do with our code actually.
> 
> When I proposed those version split, the following question occur from this
> others packagers.
> What will happen when mapserver 8 will come? (easy another package is
> created)
> 
> What will happen when mapserver 7.2 will come and if there's a breakage in
> the .map syntax?
> I'm clueless with, especially that at mapserver we were good at that jobs
> (.map breakage) at minor version change.
> 
> Maintaining package up to date, is time consuming, and also tricky when
> multiversion is involved.
> 
> So to resume :
> * Did we have a clear statement (RFC) about when .map breakage occurs, like
> only major version (perhaps we have to release more then), or major/minor ?
> If its major/minor, how much time as packager I should propose older
> versions?
> 
> * What are our project to make swing mapscript able to make versionnable lib
> ? To have php_mapscript.so.7
> python : _mapscript.so.7
> etc...
> in mapscript 7
> 
> Then for sure, if we need to have 7.0 and 7.2 separate due to .map breakage
> then versionnable lib and mapscript have to follow also Major/Minor schema.
> 
> Any thoughts ?
> 
> I'm quite new on this mailing list, so I don't know what will be the correct
> actions after there's a consensus here, like opening an rfc, and or issue.

by the way I also forget those 2 essentials things (build all in one pass)
so getting mapscript for php build for php5 and php7 and same apply for python 
(2 and 3) And guess should be the same for java (1.8, 1.9)

;-)

-- 

Bruno Friedmann 
 Ioda-Net Sàrl www.ioda-net.ch
 Bareos Partner, openSUSE Member, fsfe fellowship
 GPG KEY : D5C9B751C4653227
 irc: tigerfoot