SDK may not be version-independent for C++

[Jeff Johnson]

This came up in the context of the new version-independent stuff. The question
was whether lsb-build-c++ and lsb-build-qt4 were version-independent:

<mats> lsb-build-c++ is a question; we uplifted the base version for 4.0
 that's version is not right for targeting any earlier LSB version, though
<licquia> ok, repo rebuild seemed to fix snapshots without "fixing" the others;
will have updated repos soon
<mats> and it can't coexist with any other version of lsb-build-c++
<licquia> hmm
<mats> we also uplifted qt4 at some point (for 3.2 I guess), it also can't be
multi-version
 these are the header sets, not the stubs
<licquia> hmm
 can we generate lsb-build-c++ (and qt4) in such a way that it does the right
thing re: /opt/lsb/lib-<version>?
<-- gk4 has quit (Quit: Leaving.)
<licquia> at minimum, i suppose, we could have different package versions in
the different repos, but i'm not thrilled with that idea
 "the sdk is version independent--except for c++ apps" doesn't sound very
version-independent to me
<mats> this piece hadn't ocurred to me until I looked at that list
 I wonder how bad the c++ story actually is?
--> gk4 (~[e-mail]) has joined #lsb
<mats> (we've seen even the new version is trouble with 4.3, so it's pretty
sensitive)
<licquia> well, we've seen the g++ 4.3 thing, and now the lack of version
independence for c++
* licquia could even support something like "lsb-build-c++-3.0", "...-3.1" and
so on
<licquia> and have them all installable at the same time
<mats> we've have to tweak paths, which isn't the end of the world