Comment # 18 on bug 1102110 from Bruno Friedmann

Totally agree with Martin, we are not allowed to break the librairy policy
packaging. At least it helps, to have a old lib version this allow packages
needing it to still run.

In the case of proj (It's the first time the projet change something in the
last decade at least) it was not an easy decision to upgrade it.

We still have the problem of Leap15 having libproj12 in oss and it will not be
easy to update it (due to the number of dependencies, at least to be checked)

Having software only in devel projet, is still a complicated task to manage.
For example we shouldn't be building proj and publishing in App:Geo for Leap 15
as it has a native version in oss, and make sure that all software in App:Geo
build for Leap 15.0 will still work. But then for example 42.3 we need to build
also against the very old proj 4.9.2 published in oss. Not sure all the new
stuff in App:Geo will build and work with.

The only safe way in the future is push most of the software we need into
factory and then get them in TW and future Leap version. But we also need to
redefine App:Geo role (being a extra stable repository with no build publish
for target that have the software in oss), and make all the Devel things we
want in App:Geo:Staging or the inverse.

All of this need a maximum of actors, and contributions.