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 7BE7F138010 for ; Tue, 30 Oct 2012 20:01:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0D8E521C0CA; Tue, 30 Oct 2012 20:01:27 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 8B77421C0C5 for ; Tue, 30 Oct 2012 20:00:51 +0000 (UTC) Received: from localhost (unknown [200.89.69.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aballier) by smtp.gentoo.org (Postfix) with ESMTPSA id 3A42733D901 for ; Tue, 30 Oct 2012 20:00:49 +0000 (UTC) Date: Tue, 30 Oct 2012 17:00:41 -0300 From: Alexis Ballier To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] Dropping slotted boost Message-ID: <20121030170041.27755c91@gentoo.org> In-Reply-To: <509030E5.3090508@gentoo.org> References: <50901CB8.20301@flameeyes.eu> <20121030202426.1f6620c4@pomiocik.lan> <1910891.zYUUXR93Lo@arcarius> <509030E5.3090508@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) 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: quoted-printable X-Archives-Salt: 26227f6c-d72a-4288-a3a7-bb2e9a598323 X-Archives-Hash: c3bad0531648332b6929665ba6b9bd00 On Tue, 30 Oct 2012 15:56:21 -0400 Ian Stakenvicius wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 >=20 > On 30/10/12 03:45 PM, Tom=C3=A1=C5=A1 Chv=C3=A1tal wrote: > > Dne =C3=9At 30. =C5=99=C3=ADjna 2012 20:24:26, Micha=C5=82 G=C3=B3rny n= apsal(a): > >> On Tue, 30 Oct 2012 11:30:16 -0700 > >>=20 > >> Diego Elio Petten=C3=B2 wrote: >=20 > >>=20 > >>> So given that it's a PITA for the maintainers, a PITA for the > >>> users, eselect boost has been shown to be a bad idea and so on > >>> ... can we just go back to just install it and that's about > >>> it? > >>=20 > >> How are you going to solve the issue of a lot of packages being > >> broken with new boost versions? Are you volunteering to keep > >> fixing them with each release? > >=20 > > Simple, as any other lib, depend on older version and possibly port > > it forward. If that does not work then mask and wipe. Life goes > > on. > >=20 >=20 > If we un-slot boost there won't be an 'older' version available on > users systems anymore; when the new boost hits ~arch and then stable, > all ~arch / stable rdeps will -need- to build against that version of > boost, period (or be lastrite'd as ssuominen suggested) .... unless > i'm missing your meaning here? a sane pm wont try to upgrade to version 5 if <5 is required by some package. +1 for unslotting