1 |
Kfir Lavi wrote: |
2 |
> I would like to create those directories when the target system |
3 |
> finished the emerge. |
4 |
> The easiest is to do: |
5 |
> mkdir -p $target_dir/{proc,dev,sys} |
6 |
> inside a script. |
7 |
> Is there any mechanism that I can use to automate this without |
8 |
> running my own script? |
9 |
|
10 |
Not really.. With catalyst there are lots of hooks, but if using only |
11 |
emerge itself you will need to add that command somewhere. |
12 |
|
13 |
But, since you will need to add that command to a file somewhere |
14 |
anyway, why not add it to a script that you use to call emerge? |
15 |
|
16 |
The other thing you could do is to create an ebuild that contains |
17 |
those directories, and maybe that ebuild could also be used to list |
18 |
each and every package that you wish to install (without |
19 |
dependencies, but maybe with USE flags where significant) as an easy |
20 |
way to have a single command to create the full system. |
21 |
|
22 |
I would like to play with that myself a bit actually. |
23 |
|
24 |
|
25 |
//Peter |