| 1 |
Hi, |
| 2 |
|
| 3 |
mysql project is using https://gitweb.gentoo.org/proj/mysql-extras.git/ |
| 4 |
(i.e. an own repository) to track patches. |
| 5 |
|
| 6 |
What I like about it: |
| 7 |
|
| 8 |
1) We track patches/changes due to using a VCS. |
| 9 |
|
| 10 |
2) We can fetch directly from gitweb.gentoo.org, i.e. no need to adjust |
| 11 |
SRC_URI when changing a patch. Just push your patch, create and push a |
| 12 |
new tag, update the patch set variable and you are done. |
| 13 |
|
| 14 |
Reminds me of |
| 15 |
https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/ |
| 16 |
|
| 17 |
What I don't like about this: |
| 18 |
|
| 19 |
Cleanup is probably not that easy, the patch tarball size will increase |
| 20 |
over the time because tracking which patches are still in use can become |
| 21 |
a challenge. |
| 22 |
|
| 23 |
If you use a patch tarball the ebuild will probably don't use EAPI's |
| 24 |
default src_prepare function. You will use code like |
| 25 |
|
| 26 |
> eapply "${WORKDIR}"/patch/*.patch |
| 27 |
> eapply_user |
| 28 |
|
| 29 |
which makes it not an easy/clean task to just add *one* small/temporary |
| 30 |
patch if you need to. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Regards, |
| 35 |
Thomas Deutschmann / Gentoo Linux Developer |
| 36 |
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 |
Archives