| 1 |
On Fri, 2005-04-22 at 19:18 +0400, Kosta Todorovic wrote: |
| 2 |
> I believe Chris was giving me a solution that meant not modifying my |
| 3 |
> live portage tree at all. But I guess its not a big deal if i unmask |
| 4 |
> it in package.keywords. Could even do it temporarily. |
| 5 |
|
| 6 |
portage_conf doesn't have to point to *your* /etc/portage, just a |
| 7 |
directory with the same layout. It could point to /tmp/portage or |
| 8 |
anywhere else that you wished. |
| 9 |
|
| 10 |
> On 4/22/05, derek tracy <tracyde@×××××.com> wrote: |
| 11 |
> > Please correct me if I am wrong, but to solve your problem I would |
| 12 |
> > just create a package.keywords file to unmask libstdc++-v3 in your |
| 13 |
> > portage_conf directory. Read the examples that get emerged with |
| 14 |
> > catalyst if you need further help I can walk you through it but all |
| 15 |
> > documentation is included with catalyst. |
| 16 |
> > |
| 17 |
> > I beleive that the perk to rolling your own portage snapshot is that |
| 18 |
> > you can include your portage_overlay that you have setup on the |
| 19 |
> > computer that you are building the livecd from. |
| 20 |
> > |
| 21 |
> > e.g. |
| 22 |
> > I have sys-kernel/love-sources on my host computer's portage overlay |
| 23 |
> > directory and when I roll my own portage snapshot it includes that |
| 24 |
> > along with the normal portage snapshot. |
| 25 |
|
| 26 |
-- |
| 27 |
Chris Gianelloni |
| 28 |
Release Engineering - Strategic Lead/QA Manager |
| 29 |
Games - Developer |
| 30 |
Gentoo Linux |
Archives