Re: [RFC] Platform information services

[Isaac Dupree]

my view of the "interface breakage" problem in this project:

Either the property of the kernel you're relying on is going 
to change, or it isn't; it doesn't/shouldn't have stable 
APIs, and it will change only if there's a reason for it to 
change.  So I think the best we can do is to document what 
code relies on what properties of the kernel.  Wherever's 
appropriate and will likely be noticed and kept up-to-date. 
for example:

if you rely on a property of the kernel, you should document 
it somewhere in the kernel, and document everyone 
(hopefully) who relies on that property; or the users could 
have some symbol in the source that you can search for.  It 
doesn't have to be a function that takes up any actual 
kernel disk-space.

a bit at a distance,
-Isaac