| 1 |
On Wednesday 29 February 2012 09:46:57 Ed W wrote: |
| 2 |
> In particular I guess simply capturing the ebuilds is not sufficient and |
| 3 |
> it's necessary to capture and distribute all the source and patch files |
| 4 |
> used to create a build. The emerge tool doesn't obviously give a way to |
| 5 |
> capture this stuff. |
| 6 |
|
| 7 |
file a bug report to add a feature to do this ... something like "buildsrcpkg". |
| 8 |
it'd automatically bundle up all the eclasses the pkg is using as well as all |
| 9 |
of $CATEGORY/$PN/. |
| 10 |
|
| 11 |
> At the moment I'm using a bashrc file to grab everything from the build |
| 12 |
> directory. This seems reasonably robust for source files. However, for |
| 13 |
> patches I have considered creating a fake patch utility which would |
| 14 |
> record all the files it operates on. Any other suggestions? Perhaps |
| 15 |
> catalyst already has done something like that - not familiar with it |
| 16 |
> though? |
| 17 |
|
| 18 |
if you capture all of the $PORTDIR/$CATEGORY/$PN/ and $A, then there should be |
| 19 |
no need to manually hook into epatch to capture the patches. there's really |
| 20 |
no other place these could come from. |
| 21 |
-mike |
Archives