| 1 |
Nikos Chantziaras wrote: |
| 2 |
> Does anyone think that a mechanism of applying patches to a package |
| 3 |
> without the need to modify the ebuild of that package would be a |
| 4 |
> useful feature? There are cases of useful patches that are not |
| 5 |
> accepted by the maintainers of the ebuild (because they have not been |
| 6 |
> accepted upstream or other reasons), forcing users to copy ebuilds in |
| 7 |
> their overlay and modifying the ebuild there. This turns out to be a |
| 8 |
> hassle every time the package receives an update. |
| 9 |
> |
| 10 |
> What if we could just specify patches to be applied in, say, |
| 11 |
> /etc/portage/packages.patch with something like: |
| 12 |
> |
| 13 |
> media-video/smplayer j-random-hack.patch |
| 14 |
> |
| 15 |
> and portage would apply that patch automatically? That way, the |
| 16 |
> hassle of updating the ebuild of a package in which I use custom |
| 17 |
> patches would go away. The patches could be searched for in a |
| 18 |
> designated directory, in this example maybe |
| 19 |
> /var/portage/patches/media-video/smplayer (or something else entirely.) |
| 20 |
> |
| 21 |
> Can someone think of a way to set up something like this? |
| 22 |
> |
| 23 |
> |
| 24 |
Patches are already stored in a files directory. For instance, it would |
| 25 |
be /var/portage/media-video/smplayer/files in your example. Maybe I'm |
| 26 |
missing some point you were trying to make. |
Archives