| 1 |
Hello, |
| 2 |
|
| 3 |
On Thu, 21 Dec 2006 17:32:41 +0300 |
| 4 |
Alexander Zubkov <green@××××××××××.ru> wrote: |
| 5 |
|
| 6 |
> Hi! |
| 7 |
> I have some idea on extending portage building system (ebuild?). |
| 8 |
> Sometimes I'm (for example) want to apply custom patch to some |
| 9 |
> package. This patch can do something unusual, that can not be |
| 10 |
> accepted by maintainers and I know this. But I like features in my |
| 11 |
> patch and want it to apply automatically when updating the package. |
| 12 |
> Not to do it like this: $ |
| 13 |
> ebuild /usr/portage/pkg-categoty/some-package/some-package-1.0 unpack |
| 14 |
> $ cd /var/tmp/portage/pkg-categoty/some-package/work/... $ patch -p1 |
| 15 |
> < ~/my-patch-for-some-package $ cd |
| 16 |
> $ ebuild /usr/portage/pkg-categoty/some-package/some-package-1.0 merge |
| 17 |
> |
| 18 |
> It is lot of manual work. The idea is having an file, for example |
| 19 |
> /etc/portage/package.patch with contents like this: |
| 20 |
> =pkg-category/some-package-1* /path/to/my-patch-for-some-package |
| 21 |
> |
| 22 |
> Of course, patches could fail in newer versions. But when I'll use |
| 23 |
> that feature - I'll understand why it can be and it'll be more |
| 24 |
> convenient to maintain it. |
| 25 |
|
| 26 |
You can use portage's bashrc to do that kind of autopatching. |
| 27 |
|
| 28 |
Best regards, |
| 29 |
Yuri. |
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives