John: > The discussion started off with how are you going to notify the customer > that the interface was extremely volatile (my wording) because it is not > even supported. As I said, making it Project Private or providing the > customer with reasonable documentation and possibly a warning dialog or > compile time switch is sufficient notification also.
Would it make more sense to simply place the .pc file into a private directory, such as /usr/lib/pkgconfig/unsupported or something so that users who want to build with it can do so if they set their PKG_CONFIG_PATH to include this directory? This way users are conscious that they are linking in something unsupported if they want to build with it. I think this might be a better approach to highlighting its unstable and unsupported nature, while still allowing users to build with the interfaces. It is probably more practical than providing some sort of warning dialog at compile time. Moving forward, we can move other pc files to this directory if we determine that the interfaces are too unstable to build against for normal use. Brian
