Brian Cameron wrote:
> 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.
This has all the same issues as /usr/sfw/
Solaris looks broken or has missing bits.
Exactly what do *you* mean by "unsupported" ?
a) doesn't actually work
b) known to have issues
c) don't have resources to:
1) update to future versions
2) fix any bugs
3) will only fix security bugs
d) is EOL/EOF
e) users can use it but no developer help
1) from opensolaris.org
2) as part of a Sun Services contract
f) other, please specify
--
Darren J Moffat
