1.1

В Чтв, 27/12/2007 в 21:05 +0000, Daniel Drake пишет:
> As for other options: You could just install the patch to the filesystem 
> and require the user to apply it. Other packages do/did this, e.g. hdaps

Ok. Let's me suggest another way. I'd like to standardize (eclass) the
place such ebuilds install patches. Together with place, I'd like to add
information (may be in patch name or inside patch itself) what kernels
this patch supports. Is this the way to go?

After this I'm sure there will be no problem to have external tool to
simplify patching. If you do not like it - do not use it.

> But the only real solution is this: get the patch merged upstream, or 
> equivalent functionality offered in the mainline kernel. Everything else 
> is working against the flow of the kernel.

Eh. I see your intentions. But IMQ will never get upstream while me and
many other people are using it and AFAIK currently there is not
substitution for it (IFB is different). patch-o-matic patches are really
slow in moving to official tree, while I have to use it's functionality.
There will be always such patches.

-- 
Peter.