Looks like someone found an ABI problem, where one of the libpnd structs changed and possibly breaks dependant applications. In the end I'm not sure if it was a problem for him, but it looks like a problem others may run into.
A struct member was patched in near the top of pnd_disco_t (return from the pnd auto discovery routine, one of the main routines libpnd users depend on), rather than at the end of the struct. Usually I catch this sort of patch change and push it to the end of the struct instead ..but that one slipped through the cracks I'm afraid.
http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blob...
The problem we have is this patch came in back in May or so, so itself has been around awhile; ie: anyone building against current libpnd for thelast few months has _that_ ABI, while older apps might use the original ABI. Were it a recent patch, a decision is easier :)
So I'm on the fence.. do we move the struct member to the end so as to 'right it', or do we leave it as is since we'ev been here for awhile.
Risks either way, as we have no idea how many apps are using pre- and post- patch struct :/
At this point, its probably best to just sit on it, as some devs may have handled the ABI change themselves (if version foo do it thusly, otherwise thatly) and further changes may just mess things up more/again....
Any opinions on the matter?
jeff
-- If everyone would put barbecue sauce on their food, there would be no war.