| Summary: | kernel-2.eclass: unipatch should clean up ${WORKDIR}/patches if called more than once | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Tavin Cole <tavin.cole> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | johnm |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
ideally this shouldn't really be the practice for using unipatch. this functionality however has now been added. where possible, the patchset should just be modified to be sane before patching begins. should hit portage in the next commit (later tonight) well, i've been making heavily customized kernel ebuilds with patches gathered from various sources, and it's just easier to call unipatch multiple times. these aren't for the general public ;) thank you! |
unipatch leaves patch files laying about in ${WORKDIR}/patches. if you call it more than once from the ebuild it tries to reapply all the patches from the previous call(s), which of course fails and stops the emerge. i need to call it more than once so i can do other things in between patches (e.g. rm'ing certain files). Reproducible: Always Steps to Reproduce: 1. unipatch /path/to/patch1 2. unipatch /path/to/patch2 3. Kaboom!