Re: First motif commits

[Graham Inggs <graham@nerve.org.za>]

On 21 January 2013 22:39, Paul Gevers <elbrus@debian.org> wrote:

> Ok, let's try 3 and see where that takes us.  I'm not keen on 2 because

> there are still proprietary applications being used that need libXm.so.3
> and libXm.so.4.

 

I have still not found a single application that uses any of the Motif's XmPrint* functions.

Even the proprietary application we use (Fluent Inc. / ANSYS GAMBIT - Geometry And Mesh Building Intelligent Toolkit) was able to run against libmotif4 compiled from the current git.  This application has printing support and I was able to print to a file successfully.

None of the demos supplied with Motif make use of the printing functions either.

I am hesitant to spend a lot of time on option 3 with no way of testing.

Considering that option 1 won't break any packages in Debian, just how bad would it really be for us to release Motif to experimental without print support and without bumping the soname?  If what we did was well documented, we, or future maintainers, could reconsider options 3 and 4 should any incompatibilities arise.
 

> It seems Red Hat deprecated Xprint in 2007, it may be that the
> "official" Motif libraries are built without Xprint support.

 
Just for the record, the "official" and CentOS (and therefore RHEL too?) Motif RPMs are still built with printing support.