From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SiR0M-0006hl-9A for garchives@archives.gentoo.org; Sat, 23 Jun 2012 14:08:07 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A1875E0A5E; Sat, 23 Jun 2012 14:07:41 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 5B116E0A40 for ; Sat, 23 Jun 2012 14:07:03 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id D49351B4024 for ; Sat, 23 Jun 2012 14:07:00 +0000 (UTC) Received: by wibhn6 with SMTP id hn6so1254026wib.10 for ; Sat, 23 Jun 2012 07:06:58 -0700 (PDT) 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 Received: by 10.216.227.104 with SMTP id c82mr3121074weq.209.1340460418287; Sat, 23 Jun 2012 07:06:58 -0700 (PDT) Received: by 10.223.3.142 with HTTP; Sat, 23 Jun 2012 07:06:58 -0700 (PDT) In-Reply-To: References: <20120623142143.631d7ebf@googlemail.com> Date: Sat, 23 Jun 2012 10:06:58 -0400 Message-ID: Subject: Re: [gentoo-dev] RFC: PROPERTIES=funky-slots From: Mike Gilbert To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 86a3739e-ccf9-4a16-89bc-6f6b9ec56c54 X-Archives-Hash: 9ccea2846e28e29e2bb23ddd08825dfd On Sat, Jun 23, 2012 at 10:02 AM, Mike Gilbert wrote: > On Sat, Jun 23, 2012 at 9:21 AM, Ciaran McCreesh > wrote: >> There's been a move towards using slots for "clever" things that don't >> fit the traditional way of how slots worked. Examples include the new >> gtk2 / gtk3 handling and Ruby gems virtuals. >> >> Aside from being abusive, this screws things up for Paludis users. >> Paludis tends to bring in newer versions when possible (so that users >> aren't stuck with an old GCC forever), and allows the user to select >> when new slots are brought in. When suddenly a few packages are using >> slots and versions to "mean" something other than what they used to, >> this makes the feature unusable. >> >> Thus, as a quick workaround, I'd like to suggest adding a PROPERTIES >> value called "funky-slots", which should be set on every version of any >> package that uses slots in an unconventional manner. This probably >> doesn't need EAPI control, since package manglers are free to ignore >> PROPERTIES tokens. It won't solve the abuse, but it will allow the >> impact upon users to be lessened. >> >> -- >> Ciaran McCreesh > > I don't quite understand why this would be necessary. > > Would "funky-slots" just be used in situations where ebuilds with the > same PV but different PVR have different slots? > > Taking the gtk2/gtk3 example, I think the -r200/-r300 thing is only > used in libraries; applications use slot deps to select which one they > need. Paludis should not remove the -r200 version if it is still > referenced in the depgraph, correct? Or maybe you are saying that Paludis will not automatically install a new slot for a package that is already installed, even when referenced by a slot dep?