From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5EB1513877A for ; Sat, 26 Jul 2014 05:21:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0C5A6E0C1B; Sat, 26 Jul 2014 05:21:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 29485E0C0C for ; Sat, 26 Jul 2014 05:21:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 7128D3400EF for ; Sat, 26 Jul 2014 05:21:48 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -1.505 X-Spam-Level: X-Spam-Status: No, score=-1.505 tagged_above=-999 required=5.5 tests=[AWL=-0.802, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ix0moj4ED-yT for ; Sat, 26 Jul 2014 05:21:42 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id B5C5A3400DC for ; Sat, 26 Jul 2014 05:21:42 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XAuQM-0002eZ-EM for gentoo-dev@gentoo.org; Sat, 26 Jul 2014 07:21:38 +0200 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Jul 2014 07:21:38 +0200 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Jul 2014 07:21:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: don't rely on dynamic deps Date: Sat, 26 Jul 2014 05:21:26 +0000 (UTC) Message-ID: References: <53CD6BED.10603@gentoo.org> <20140722234748.021d8a09@gentoo.org> <20140726000958.0e7f0f95@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT d447f7c /m/p/portage/src/egit-src/pan2) X-Archives-Salt: caedb018-aae0-4a8b-b8a6-d2e9a0ab4728 X-Archives-Hash: 25ed1491e6b983b6ead546af6eef6bdf Tom Wijsman posted on Sat, 26 Jul 2014 00:09:58 +0200 as excerpted: > EAPI specifies what PMs need to conform to, not the other way around; > EAPI-0 may very well be derived from Portage, that doesn't make such > side features that have not been specified in EAPI-0 a part of EAPI-0. Not being around at the time, you may not know some of the history, but feel free to ask Ciaranm if you need a more authoritative source. The thing is, EAPI-0 was not originally completely specified, and to my knowledge, remains that way, because that would have been real-world essentially impossible to do. Instead, a convenient shortcut was taken. EAPI-0 was defined as what portage did at the time, with EAPI-1 for sure and I believe EAPI-2 at least, being defined as the the previous EAPI, with specifically defined changes, but with the base EAPI still only fuzzily defined as, basically, what portage did at the time. And since the beginning, while there have been other unapproved EAPIs not allowed in the main gentoo tree, because portage was and remains the official default PM, no EAPI has been approved for main-tree deployment until portage had a working implementation. So while portage can and certainly does have bugs where it doesn't meet EAPI requirements, particularly for behavior there since EAPI-0 and not specifically defined to be different in a specific EAPI since then, to the extent that PMS applies at all, the interpretation of PMS must still be read in the context of what portage did all those years ago with the original EAPI-0 spec, since EAPI-0 was /defined/ based on portage behavior at the time. Which then begs the question[1] I asked, how old /is/ this dynamic-deps behavior? Does it extend back to EAPI-0? My gut sense from memory as a user back then and now is that it does, but that's simply a gut sense I'm ill equipped to go back and verify. --- [1] Begs the question: Yes, I'm aware of the legal and philosophical "circular logic" usage, now generally legacy in terms of real-world use except in the philosophic and legal areas. I deliberately choose to use the phrase in the newer and now much more common sense, rhetorically personifying the question such that it can "beg to be asked". -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman