Going through build scripts for dependency/helper application like xmedcon, I was building them against gtk2 last year for both tde13 and R14. Do we have any 'tde' standard we are trying to enforce for minimizing the dependencies for a complete tde install?
What I mean is that if someone goes to install tde-full with all helper apps, do we want and try to say all apps with a gtk requirement should be built against gtk3 instead of gtk2? I for one prefer gtk2, but I can see the logic in standardizing around a version to minimize dependencies (and to prevent build failures when gtk2 is dropped)
Has anyone given this any thought? I don't like the prospect of having to recode older apps against a new gtk, but it is doable. The number of apps this will apply to is minimal.
What is a "helper app"?
Apps like xmedcon are outside the scope of Trinity. Distro packagers and maintainers ensure the dependencies are satisfied.
Darrell
On 01/13/2014 02:16 PM, Darrell Anderson wrote:
What is a "helper app"?
Apps like xmedcon are outside the scope of Trinity. Distro packagers and maintainers ensure the dependencies are satisfied.
Darrell
Well, I'm getting old I guess,
tde-libksquirrel has xmedcon as an optional dependency that provides medical image handling and conversion. (CT, MRI, PET, etc..) I always build it because I use the functionality. My question was for these type of applications is whether there is any preference whether they are built against GTK2 or GTK3 if we have a choice.
The reason it matters to me is that if some apps are built with a gtk2 dependency, you pull in gtk2 as a build dependency, if against gtk3, then you pull in gtk3. (that looks like it will happen for the foreseeable future anyway). I didn't know if there had been any discussion about trying to minimize build dependencies such that if an option existed to use either gtk2 or 3, if there was a preference for one or the other.
Smacks self -- there I go thinking someone else will actually be building tde on arch except me -- never mind...