>
>
>     Installer mantis ensureFix: 4874.
>
>
>
> Wouldn't it be best to get this fix loaded into the Montecello 
> repository as a proper change, so that the Universe just has to point 
> at the new version?
>
Of course it would be best, but this is a kernel extension, which is 
under the control of the release team, not I.

I discovered that, while waiting for such things to to be integrated 
into the kernel, I have found myself writing my code to be as generic as 
possible instead.

As an example: I find myself writing code which avoids using split/join 
until split/join is a generically available feature. This may be a long 
wait for it to be added to 3.10, but it will never be added to 3.9, 3.8 
or 3.7 so.

If I keep on doing this, it means that all efforts to improve the kernel 
are wasted, because even if I write a kernel improvement, I am 
conditioned by the working context to not use such extensions until they 
are deemed acceptable  by the consensus, which in the case of "Message 
eating Null", or Gorans name space improvements is probably never.

This has been bugging me for a while so, I figure the only way I can see 
to get around this is to legitimize the idea of a kernel-patch in the 
universe (which formalizes which versions the patch is applicable to) 
and have it managed properly in mantis, i.e. feedback discussion. new 
versions etc.

With this in place I feel that I can then get on and use it without 
shame. If it is found that lots of essential packages make use of that 
patch then this would be a good case for getting it included by the 
release team.

just my 2p

Keith