1 |
I believe Chris was giving me a solution that meant not modifying my |
2 |
live portage tree at all. But I guess its not a big deal if i unmask |
3 |
it in package.keywords. Could even do it temporarily. |
4 |
|
5 |
On 4/22/05, derek tracy <tracyde@×××××.com> wrote: |
6 |
> Please correct me if I am wrong, but to solve your problem I would |
7 |
> just create a package.keywords file to unmask libstdc++-v3 in your |
8 |
> portage_conf directory. Read the examples that get emerged with |
9 |
> catalyst if you need further help I can walk you through it but all |
10 |
> documentation is included with catalyst. |
11 |
> |
12 |
> I beleive that the perk to rolling your own portage snapshot is that |
13 |
> you can include your portage_overlay that you have setup on the |
14 |
> computer that you are building the livecd from. |
15 |
> |
16 |
> e.g. |
17 |
> I have sys-kernel/love-sources on my host computer's portage overlay |
18 |
> directory and when I roll my own portage snapshot it includes that |
19 |
> along with the normal portage snapshot. |
20 |
> |
21 |
> On 4/22/05, Kosta Todorovic <kostodo@×××××.com> wrote: |
22 |
> > > Yes. It will be made from your $PORTDIR, wherever that may be. |
23 |
> > |
24 |
> > What are the advantages of using the live portage tree rather than a |
25 |
> > downloaded snapshot? |
26 |
> > Is it possible to use a downloaded snapshot and put an overlay to make |
27 |
> > a new snapshot? |
28 |
> > Is there any point of doing this? |
29 |
> > |
30 |
> > -- |
31 |
> > gentoo-catalyst@g.o mailing list |
32 |
> > |
33 |
> > |
34 |
> |
35 |
> -- |
36 |
> gentoo-catalyst@g.o mailing list |
37 |
> |
38 |
> |
39 |
|
40 |
-- |
41 |
gentoo-catalyst@g.o mailing list |