From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-84580-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id 377351382C5
for <garchives@archives.gentoo.org>; Sat, 12 May 2018 13:48:17 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id C80BBE0ACE;
Sat, 12 May 2018 13:48:10 +0000 (UTC)
Received: from mail-pl0-f54.google.com (mail-pl0-f54.google.com [209.85.160.54])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 689EAE0AC8
for <gentoo-dev@lists.gentoo.org>; Sat, 12 May 2018 13:48:10 +0000 (UTC)
Received: by mail-pl0-f54.google.com with SMTP id i5-v6so4836269plt.2
for <gentoo-dev@lists.gentoo.org>; Sat, 12 May 2018 06:48:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=/VUXXdZBucPMuNPOfaCDHT/Flggn8FRt54SWywub5ng=;
b=ry9ujlnrxFNE9niFf6e3vHL/L3xfQ/zNgKqxCA/bIJ92GPbzIJjOLQ3YuPok27QHnc
cqL7TyD5CtZPv9ceSjnCDhUQtdoTpwwGF1sknexvc+6x6TCgXe154mpqesYtSM/T5hsP
5dRtJZDM6hW52TXFUIVSVR4FQMgcNebNWojDpGMHTv+lqg7dTi10wOKc9FAdbgHl544/
wEY7Y/rvVThYmvznc1JP//o0vdjFhQPy+7j6UmME1DbluQAEVf5KNpYxeS/BNH8x64D9
iKGl9yzpBVMcJmFuK+OMbghgE6LAVMulHoWu7KFiKDZZKGPhKyXuK+83jMc5ebpg3pz6
ySRg==
X-Gm-Message-State: ALKqPwdcCEPDguKjKtSUF2Uq+avuoDLATKeMvwglEaP1RNts1GwSNbtB
k1BRbTS5g1Dxq1ZIzg8pEcWwbrYzNMvnutzgkwT68Q==
X-Google-Smtp-Source: AB8JxZpONOL5FCcPmqOqzLllmTrQyhcZFNc8egTR+Jb+YBA72aB4AJFfF16JGjZC5OFI2RDuZDTAX2h7IbxIpjygVeo=
X-Received: by 2002:a17:902:8f84:: with SMTP id z4-v6mr2616413plo.194.1526132888908;
Sat, 12 May 2018 06:48:08 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
References: <2532421.f3YmpD0exa@gump>
In-Reply-To: <2532421.f3YmpD0exa@gump>
From: Rich Freeman <rich0@gentoo.org>
Date: Sat, 12 May 2018 09:47:57 -0400
Message-ID: <CAGfcS_n04uCw1k4jPoLjvo0sVAyhz-+Dz-K9XjC56oyfG_VM1A@mail.gmail.com>
Subject: Re: [gentoo-dev] [RFC] multiversion ebuilds
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset="UTF-8"
X-Archives-Salt: 57834c17-616b-424e-af5a-b5c0ed8b0733
X-Archives-Hash: 1cf2907e8f5995133f66540d83910791
On Sat, May 12, 2018 at 8:20 AM Gerion Entrup <gerion.entrup@flump.de>
wrote:
> Different version keywording can be done as before:
> ```
> if [[ ${PV} == "3.1" ]] ; then
> KEYWORDS="~amd64 ~x86"
> else
> KEYWORDS="amd64 x86"
> fi
> ```
From a readability standpoint I could see this getting out of hand if we
aren't careful. Also, we'd want to keep this simple enough that the simple
act of stabilizing a package doesn't introduce regressions (perhaps even in
versions that we don't intend to touch). We'd also need rules about
conditionals so that the metadata cache works.
You also would need to be careful about ebuild revisions in general, since
you're potentially affecting multiple versions at the same time.
How would revbumps fit into this? All kinds of bad things can happen by
editing ebuilds in place, and this would compound the issue.
(Don't get me wrong - the concept is interesting...)
--
Rich