1 |
On Thu, Oct 03, 2002 at 11:45:40AM +0200, Christian Plessl wrote: |
2 |
> Hi |
3 |
> |
4 |
> I would like to create and contribute some ebuild that are missing so far. |
5 |
> |
6 |
> Althought there is some documentation on creating ebuilds, there are still |
7 |
> things I dont understand so far. It seems, that I will have to learn from |
8 |
> the example of other ebuilds. |
9 |
> |
10 |
> Is there a safe way, how I can create and test my ebuild? (Without the risk |
11 |
> of screwing up my gentoo installation, which works really perfect so far!) |
12 |
> |
13 |
|
14 |
Make a portage overlay directory and set the variable PORTDIR_OVERLAY |
15 |
to point to it. This will keep your own ebuilds from being deleted |
16 |
when you do an emerge rsync. This should look just like your normal |
17 |
portage directory (ie, put your ebuilds in |
18 |
$PORDIR_OVERLAY/app-misc/appname) to get it to work. To see if your |
19 |
ebuild is seen after you do this, do an emerge -s appname and it will |
20 |
tell you if it finds it. |
21 |
|
22 |
Next, look at the man page for ebuild, which can be used to perform |
23 |
the necessary steps individually instead of having emerge do them all |
24 |
at once. Then you can test each section of the ebuild without doing a |
25 |
full install. |
26 |
|
27 |
-- |
28 |
burton |