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 F299713875F for ; Wed, 30 Jan 2013 08:35:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3F38A21C01A; Wed, 30 Jan 2013 08:35:23 +0000 (UTC) Received: from spot.xmw.de (spot.xmw.de [176.9.87.236]) by pigeon.gentoo.org (Postfix) with ESMTP id 2E425E04EB for ; Wed, 30 Jan 2013 08:35:22 +0000 (UTC) Received: from [IPv6:2001:6f8:1cd1:0:21d:72ff:fe88:9ac1] (x.l.xmw.de [IPv6:2001:6f8:1cd1:0:21d:72ff:fe88:9ac1]) by spot.xmw.de (Postfix) with ESMTPSA id DE03C14410AFF for ; Wed, 30 Jan 2013 09:35:20 +0100 (CET) Message-ID: <5108DB40.6060108@gentoo.org> Date: Wed, 30 Jan 2013 09:35:12 +0100 From: Michael Weber User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130114 Thunderbird/17.0.2 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 To: gentoo-dev@lists.gentoo.org Subject: Multilib approach(es) Re: [gentoo-dev] The gx86 multilib project -- masterplan References: <20130127161237.1a04614e@pomiocik.lan> <1359302900.2927.30.camel@belkin4> In-Reply-To: <1359302900.2927.30.camel@belkin4> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 9121f91b-20f5-4d51-ad09-bf2ccf63fe99 X-Archives-Hash: 3e375bcbebd899f9764cbf831e027186 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, What's the primary Idea behind multilib at all? Isn't it just a workaround to keep prebuild software from lazy/incapable/dead upstreams working (skype, ...)? Is there any other real use besides bragging about processor capabilities and compiling an stage1 boot loader? Please don't get me wrong. I honor the whole effort done to bring this magic into portage/..., but I see limits in the underlying file system. The current solution suggested by FHS-2.3 [1] is to use /lib and /usr/lib, which works for runtime emul- packages, since software either installed to /opt/{${PN},bin} or had no alternative in /bin or /usr/bin. On 01/27/2013 02:40 PM, Thomas Sachau wrote:> 2. How do you handle other abi-specific files like headers or binaries > and cases like binaries with abi-specific content? Is it possible > to preserve them for all requested abis or to preserve them for an > non-default abi? On 01/27/2013 05:08 PM, Pacho Ramos wrote:> Maybe installing headers in other place would be interesting :/ This is getting wired now, when we get an x86, x86_64 and x86_32 (srsly?) implementation of cp(1). Either we avoid collision python style with /bin/${PN}- and some link magic, to select the "best" according to moon phases. In the spirit of FHS, I thought about introducing /bin for some time, but this continues with other dirs. We would need /var/lib as well (/var/lib/munin/ has ABI specific .rrd files), /usr/include/ ... wait a minute. What about separating these ABIs on top dir and keeping the respective sub-trees clean, like //{,usr/}{bin,lib}? // could be realised by one of these systems - - chroot (just like / chroots), needs root. - - Gentoo/PREFIX style - - modified runtime linker to pic correct LD_LIBRARY_PATH. These // can be anything, like different ABIs, different libc implementations, different keyword (stable, testing), different Distros, - as long as it runs with the current kernel. Well, thin-provisioning, qemu, *random virtualization*. One ABI, maybe the one that can run/chroot all others sould be defined as qual="", just like non-multilib systems. Replication of //{home,usr/portage} can be avoided by symlinks or bind-mounts, or hardlinks. (Srsly, /usr/portage/"ebuilds,profiles,metadata,caches" has to be in /var/portage.) It'd be a pretty good solution for restraining mentioned (malicious) software, /skype/ for example. Some roundups have to be made for exhausive $PATH, X11 .desktop files, to enable starting other // Comments? [1] http://www.pathname.com/fhs/pub/fhs-2.3.html - -- Michael Weber Gentoo Developer web: https://xmw.de/ mailto: Michael Weber -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlEI20AACgkQknrdDGLu8JAGBAD+MPkmNxKSCrHcAnj5PUaxyTM1 Hhymj3cHaxBuTFHlK78A/2t5qJNyg1c0nc6FSePKXq+MXWp/RVDWMb5XCpfEh4dR =xmPN -----END PGP SIGNATURE-----