| 1 |
Neil Bothwick wrote: |
| 2 |
> Overlays are there specifically for people who need |
| 3 |
> something different from the standard portage tree. They are |
| 4 |
> hardly difficult to use, |
| 5 |
|
| 6 |
Not difficult, but it is clumsy: |
| 7 |
|
| 8 |
mkdir -p /usr/local/portage/category/package |
| 9 |
## Dont't copy all ebuilds, just the one to be tweaked: |
| 10 |
cp /usr/portage/category/package/packag-x.y.z.ebuild /usr/local/portage/category/package/ |
| 11 |
## Copy all possible patches: |
| 12 |
cp -a /usr/portage/category/package/files /usr/local/portage/category/package/ |
| 13 |
## Copy the new patch too: |
| 14 |
cp package-foo-bar.patch /usr/local/portage/category/package/files/ |
| 15 |
## Edit the ebuild and insert an 'epatch ${FILESDIR}/package-foo-bar.patch' command: |
| 16 |
vim /usr/local/portage/category/package/package-x.y.z.ebuild |
| 17 |
[search for src_unpack(), insert extra command at end, :wq] |
| 18 |
## Recreate digest: |
| 19 |
ebuild /usr/local/portage/category/package/package-x.y.z.ebuild digest |
| 20 |
## Finally, emerge the thing: |
| 21 |
emerge -1 package |
| 22 |
|
| 23 |
> How hard is that? |
| 24 |
|
| 25 |
Not hard, but a nuisance. Of course one could write a script that automates all |
| 26 |
those seven steps into a single command, but it has proven a bit beyond my skills |
| 27 |
(the finding of the category when just saying 'ovlay.sh package', not to mention |
| 28 |
the insertion of an epatch command). Bo once said (or was it someone else?) he |
| 29 |
had such a script. If so, Bo, please post the script. Or better yet, push it |
| 30 |
upstream. Portage knows about overlays, but doesn't have any commands to make |
| 31 |
working with them easy. It really should include a command that copies the latest |
| 32 |
ebuild of a given package to an overlay, and inserts epatch commands for all the |
| 33 |
additional arguments. |
| 34 |
|
| 35 |
Benno |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives