From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1F2VJp-0001Mh-Dg for garchives@archives.gentoo.org; Fri, 27 Jan 2006 15:15:21 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k0RFEAow005456; Fri, 27 Jan 2006 15:14:10 GMT Received: from gw.open-hosting.net (gw.open-hosting.net [65.64.29.89]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k0RFB5rM012939 for ; Fri, 27 Jan 2006 15:11:06 GMT Received: from speedy.apps4med.net ([66.139.177.227]) by gw.open-hosting.net (8.13.4/8.13.3) with ESMTP id k0RFAuwf022381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 27 Jan 2006 09:11:02 -0600 Message-Id: <200601271511.k0RFAuwf022381@gw.open-hosting.net> From: MIkey Subject: [gentoo-dev] Re: Re: Re: Re: Re: Re: bootstrapping since gcc 3.4 is stable To: gentoo-dev@lists.gentoo.org Date: Fri, 27 Jan 2006 09:08:48 -0600 References: <43D901F3.3010701@egr.msu.edu> <200601261733.k0QHWuGX012623@gw.open-hosting.net> <200601270942.14427.pauldv@gentoo.org> User-Agent: KNode/0.10 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on gw.open-hosting.net X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.0.4-gr0 X-Spam-Checker-Version: SpamAssassin 3.0.4-gr0 (2005-06-05) on gw.open-hosting.net X-Archives-Salt: 9a3a1fb6-5f72-42cf-8075-8ba851988ea7 X-Archives-Hash: e7602e2072571d1fac003171d51127b2 Paul de Vrieze wrote: > The ebuilds are not done in that way, the problem is portage's inability > to handle this. There is no way ebuilds could solve this problem except > not having the dependency. What is needed to solve it is merge perl > without ssl support, merge openssl, merge perl with ssl support. This is > however not clear to portage, so it doesn't know how to solve this. Such > dependencies are mainly present in system, so starting from a stage 3 > solves all these problems. This bug (39318) has persisted since 2004-01-25, with the most recent bite reported on 2005-12-07. It is not a problem unique to stage1 or stage3. Since portage apparently does not always handle circular dependencies gracefully, the problem is not solved by a stage3 install, it is deferred. Regardless, it can more easily be accounted for in bootstrap.sh than tearing up portage completely. It still has to be accounted for to build the official stage3 releases. Lastly, for some reason I have not run into this particular problem when building from stage1 for a while now. No way? I get the feeling that anything is possible :) -- gentoo-dev@gentoo.org mailing list