1 |
On Sat, 18 Apr 2009 21:23:24 -0500 |
2 |
Paul Hartman <paul.hartman+gentoo@×××××.com> wrote: |
3 |
|
4 |
> ebuild /usr/portage/foo-bar/yourpkg-1.2.3.ebuild unpack |
5 |
> ebuild /usr/portage/foo-bar/yourpkg-1.2.3.ebuild prepare |
6 |
> ebuild /usr/portage/foo-bar/yourpkg-1.2.3.ebuild configure |
7 |
> ebuild /usr/portage/foo-bar/yourpkg-1.2.3.ebuild compile |
8 |
> ebuild /usr/portage/foo-bar/yourpkg-1.2.3.ebuild preinst |
9 |
> ebuild /usr/portage/foo-bar/yourpkg-1.2.3.ebuild install |
10 |
> ebuild /usr/portage/foo-bar/yourpkg-1.2.3.ebuild postinst |
11 |
|
12 |
One doesn't need to perform these steps explicitly; when one performs |
13 |
a command like merge, ebuild also performs all commands that |
14 |
normally precede merge. |
15 |
|
16 |
So I think that if he wants to tweak the source code before compiling, |
17 |
the easier way would be to issue a unpack command, tweak the source, |
18 |
then issue a merge command. |
19 |
|
20 |
But I think it would be much better to write a patch, |
21 |
or simply modify the distfile and create a new ebuild that |
22 |
uses the modified distfile. |
23 |
|
24 |
-- |
25 |
Software is like sex: it is better when it is free. --Linus Torvalds |