Re: [gentoo-catalyst] Problem with NMAP

[Ryan Lynch]

Yea, this has to do with a big change in portage.  IMHO, the need to put out an announcement when they make such a big change.  When you make a change like this, you know there are going to be a bunch of ebuilds that have incorrect/incomplete manifests that have gone unnoticed, and are going to be giving everybody problems.  But instead of making an official announcement about the change, they keep the information almost hidden from most people, and have caused myself and others considerable frustration.  I'm just annoyed thats all, because I'm using catalyst and other meathods to build some install media, and I ran into a bunch of these bad manifest errors before I was told about the change in portage.  Just my two cents.

On Mon, 25 Apr 2005 03:08:35 -0400
Robert Paskowitz <r2d2@g.o> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> You need to 'ebuild libstdc++-v3-3.3.3-r1.ebuild digest' to create a new
> Manifest file. This will have to be done before any catalyst stuff, in
> the directory with the ebuild, and the base directory should be in your
> make.conf's PORTDIR_OVERLAY.
>
> Or, you could export FEATURES="-strict" in your catalyst envs to lower
> the amount of verification performed, but I recommend the first method.
>
> Robert
-- 
gentoo-catalyst@g.o mailing list