List Archive: gentoo-catalyst
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
I've added a portage overlay with a unmasked libstdc++ ebuild and
added libstdc++ to livecd-stage1.spec but when i build livecd-stage1 i
get the following error:
!!! Digest verification Failed:
!!! Reason: Filesize does not match recorded size
On 4/22/05, Chris Gianelloni <email@example.com> wrote:
> On Fri, 2005-04-22 at 19:18 +0400, Kosta Todorovic wrote:
> > I believe Chris was giving me a solution that meant not modifying my
> > live portage tree at all. But I guess its not a big deal if i unmask
> > it in package.keywords. Could even do it temporarily.
> portage_conf doesn't have to point to *your* /etc/portage, just a
> directory with the same layout. It could point to /tmp/portage or
> anywhere else that you wished.
> > On 4/22/05, derek tracy <tracyde@...> wrote:
> > > Please correct me if I am wrong, but to solve your problem I would
> > > just create a package.keywords file to unmask libstdc++-v3 in your
> > > portage_conf directory. Read the examples that get emerged with
> > > catalyst if you need further help I can walk you through it but all
> > > documentation is included with catalyst.
> > >
> > > I beleive that the perk to rolling your own portage snapshot is that
> > > you can include your portage_overlay that you have setup on the
> > > computer that you are building the livecd from.
> > >
> > > e.g.
> > > I have sys-kernel/love-sources on my host computer's portage overlay
> > > directory and when I roll my own portage snapshot it includes that
> > > along with the normal portage snapshot.
> Chris Gianelloni
> Release Engineering - Strategic Lead/QA Manager
> Games - Developer
> Gentoo Linux
firstname.lastname@example.org mailing list