1 |
Currently, I just use /usr/portage and modify/add ebuilds there in the |
2 |
appropriate path. Then 'ebuild /usr/portage/.../.../myebuild.ebuild |
3 |
digest', 'emerge metadata' and 'catalyst -s mytag' do the job for |
4 |
livecd-stage2. |
5 |
|
6 |
Greetings, |
7 |
|
8 |
Georg |
9 |
|
10 |
Kessler, Paul wrote: |
11 |
> I added portdir_overlay to my make.conf on the build system and did |
12 |
> create a new snapshot. This didn't seem to do anything at all. |
13 |
> |
14 |
> -----Original Message----- |
15 |
> From: thibaut legendre [mailto:quantique@××××××××××.fr] |
16 |
> Sent: Thursday, September 15, 2005 3:46 AM |
17 |
> To: gentoo-catalyst@l.g.o |
18 |
> Subject: Re: [gentoo-catalyst] Portage Overlay |
19 |
> |
20 |
> Kessler, Paul wrote: |
21 |
> |
22 |
> |
23 |
>>I have a custum package that I would like emerged during the stage |
24 |
>>2 build. On my development system I just do a simple portage |
25 |
>>overlay to get my package in the mix. Will I need to manually |
26 |
>>create the overlay in the fsscript or is there a better mechanism |
27 |
>>to handle this task? |
28 |
>> |
29 |
>>Paul |
30 |
> |
31 |
> |
32 |
> Why not add your overlay directory when you create your snapshot using |
33 |
> "portdir_overlay: /my/overlay/directory" ? |
34 |
> |
35 |
-- |
36 |
gentoo-catalyst@g.o mailing list |