https://bugzilla.novell.com/show_bug.cgi?id=213927
jsmeix@novell.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |danw@novell.com
------- Comment #3 from jsmeix@novell.com 2006-11-10 01:39 MST -------
1.
To test what about the PPDs is known to the cupsd use
root@host# lpinfo -l -m
Attach the output of this command as mime type text/plain to this bug.
2.
Verify that Gnome does not use non-public CUPS API calls.
There have been API changes from CUPS 1.1.x to 1.2
regarding non-public CUPS library functions.
See http://www.cups.org for details
Here from a mail from the CUPS main author:
------------------------------------------------------------------------------
From: Michael Sweet
After my investigation, I think r4683 and r4741 changes of CUPS 1.2 make libcups API incompatible with older libcups.
For example the change from cups_strlcpy to _cups_strlcpy breaks the combination of cupsd 1.1 and libcupsys 1.2.
We work very hard to not break binary compatibility with *public* APIs. Since those emulation functions are a) not public APIs and b) not available on all systems (i.e. they only show up if your platform doesn't provide the named functions), they aren't considered for the library version number. Non-CUPS programs using these functions should expect to fail at random times depending on the version of CUPS that is installed...
Although such mixture is rare case, I think it's better to bump up the soname version if you remove an exported function or change its argument against the libraries.
Doing so will cause unnecessary breakage of all existing applications. The CUPS CMP (now called the CUPS Developer Guide) has always documented the rules for naming of public APIs, and we have NEVER documented private APIs to avoid their use. ------------------------------------------------------------------------------ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.