Summary: | patch_o_matic ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Belt <gaarde> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | mholzer, sogard |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul Belt
2003-02-08 13:43:18 UTC
One tiny problem: you need the source of iptables too, I think is completely useful if is not compiling the iptables automatically. Also seem that lot’s of patch-o-matic logic is kind of fuzzi and sometimes will allow you to patch a kernel 2.6 with a 2.7 patch and other funny stuffs. I propose a rewrite of patch-o-matic in portage way. I don’t know exactly how but I am thinking at something that iptables packet will depend and will patch the kernel and iptables just using ther USE. > One tiny problem: you need the source of iptables too
AFAIK you don't need iptables source because you can compile it with extensions use flag.
Err... We have net-misc/l7-filter and net-firewall/ipp2p; there's no way we could support the experimental stuff in patch-o-matic, and patching the kernel in a unpredictable way has a potential of causing lots of trouble for other ebuilds. WONTFIX. |