[KARMIC] UBUNTU: updated compcache version to 0.5.3

[Stefan Bader]

Tim Gardner wrote:
> Stefan Bader wrote:
>> This actually renames both modules. While this is maybe the way of following 
>> upstream have you thought of:
>>
>> - will the users (and by that I mean the something like the installer)
>>    need changing.
>> - also before both old modules were controlled by seperate config options
>>    CONFIG_TLSF and CONFIG_BLK_DEV_COMPCACHE (both having some suboptions).
>>    Now ramzswap.ko and xvmalloc.ko will be created only based on the setting
>>    of CONFIG_BLK_DEV_COMPCACHE. The Kconfig file still refers to TLSF, so this
>>    needs cleanup (either way). Actually Kconfig seems to be terribly out of
>>    sync with reality.
>> - The Changelog says that a parameter also got changed (backing_dev ->
>>    backing_swap. Along with the module renames we have to make pretty sure we
>>    do not break something/-one.
>>
>> Stefan
>>
> 
> Applied with Kconfig cleanups, though I'll be danged if I can figure out
> what is important about 'config TLSF'. If you delete that clause, then
> the ubuntu/compcache directory isn't built. Maybe one of you guys can
> eyeball it.

That really sound odd. Andy wanted to have a second eyeball on it.
To me it seemed like just forgotten.

> Stefan - I think there have been several external changes to this
> driver, so its likely we'll have regressions (or at least changes in
> behavior) regardless of the name of the module. AFAIK we've never made
> any promises about third party module ABI or name stability.

Right, I was not so much afraid of changing an abi but more to have it cleaned 
a little before upgrading and to make us remember to tell those that are 
affected by the changes. Not sure how well this can be done beyond users inside 
the company. Maybe at least a notice on the installer list.

Stefan

> rtg


-- 

When all other means of communication fail, try words!