On 18-Dec-05, at 4:30 PM, Martin Konold wrote:
But it adds another runtime requirement to the application. When using
traditional linking this means that the application will fail at
runtime if
the appropriate cups client library is not available.
Yes, and this is a limitation of the Linux linking model that I think
should be addressed with some urgency, if it is a goal to make it
easier for ISVs to adopt new Linux-desktop capabilities
aggressively. (I think that it should very much be a goal, since it
has been and continues to be hard for ISVs to integrate well with the
"latest" of a given desktop, without making that a runtime
requirement or exploding out their build-and-ship configs. Our GNOME
file dialog trail of tears is but one example of many, I'm sure.)
Maybe this is something like relaytool to wrap all the dlopen
machinations necessary to emulate DT_USEFUL, but I bet that gets
extremely exciting for those of us silly enough to use C++. Maybe
this is fixing the toolchain to support a DT_USEFUL-alike directly.
Maybe it's adoption of something like Miguel's recent web desktop
hobby-horse, though I think that's probably a level of abstraction
(sorry: "service orientation") above what's hurting ISVs most today.
(I had a whole schpiel about this ready for the meeting, but never
got a chance to deliver it, so you'll have to imagine me being
charming and displaying my impressive comic timing to really get the
full effect.)
Mike
_______________________________________________
Desktop_architects mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/desktop_architects
