From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-63170-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 365871381F3
	for <garchives@archives.gentoo.org>; Tue, 15 Oct 2013 17:31:19 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 8426BE09FB;
	Tue, 15 Oct 2013 17:31:14 +0000 (UTC)
Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id CC66FE0997
	for <gentoo-dev@lists.gentoo.org>; Tue, 15 Oct 2013 17:31:13 +0000 (UTC)
Received: by mail-vb0-f52.google.com with SMTP id f12so5235431vbg.39
        for <gentoo-dev@lists.gentoo.org>; Tue, 15 Oct 2013 10:31:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:content-type;
        bh=qnXTeKuHk7TMo+cBOfrgK3/9sfLVMbEojrgNnYwMrLQ=;
        b=AVYU/K946+3QGYXC/lLRRJ3nsn8tkfEhf7avAjDINphOGqBnnLCvdTGkfJF8P+ZlOl
         Zscuwf7FWXJY/7ONBTFhIo3QY9sM23LEY/Jk7TlcLlPuEBYkhPXsaInslPP4ZJjv6egG
         obJrDdCz1cu2VIiRH2p/ibt+nrsORPkr1nQMEXg1anWa9iXmU/Z2ZLQvJ4505TJqFG93
         SXfMP5bUx6D3XU+gCt6kSefd0PJAhiRu5pag9voMh/ALKuvY0cgMzfGl1GPAUA7Eh9ll
         PHTjgJTYQi5hN327LvCnbMo3zGIatQ+XNF78ETfmutVStuqybhNi8XTuVmNB+D9mA7jy
         TUUg==
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
X-Received: by 10.58.254.200 with SMTP id ak8mr13198287ved.12.1381858272953;
 Tue, 15 Oct 2013 10:31:12 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.52.108.199 with HTTP; Tue, 15 Oct 2013 10:31:12 -0700 (PDT)
In-Reply-To: <20131015190422.6f2570f4@porcupinefactory.org>
References: <20131015190422.6f2570f4@porcupinefactory.org>
Date: Tue, 15 Oct 2013 13:31:12 -0400
X-Google-Sender-Auth: dzWQcfvYulGxPy-sdbTiAXHFFrQ
Message-ID: <CAGfcS_nYs=fNSR4uNWekbfeinAEA6v6tnqG-ruE9H-jBG2k4BQ@mail.gmail.com>
Subject: Re: [gentoo-dev] Broken ebuilds
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Archives-Salt: 5378a42f-b3ec-46d1-919a-c9460e409d79
X-Archives-Hash: afae9f5d05014fabe32f4b41d8704c3b

On Tue, Oct 15, 2013 at 1:04 PM, P.C.
<gedeli.pasc.pcz@porcupinefactory.org> wrote:
>
> Is that "ebuild decay" intentional? How long I can expect ebuilds to
> stay useful?

There really are no guarantees for anything not in the current tree.
The EAPIs/eclasses themselves are pretty well-designed and while
breakage over a period of years is likely, over a period of months it
is not.

However, your problem is that a patch set was hosted only on mirrors
and not anywhere more permanent.  In general mirror-only patch hosting
is frowned upon - they should have a SRC_URI that doesn't start with
mirror://.  However, that doesn't guarantee that those patches will be
hosted forever.  I keep them in my gentoo webspace and don't really
rush to clean them up, but that space is not archived anywhere.

Google suggests that you might be in luck if you manually fetch your
file from here:
http://dev.gentoo.org/~floppym/python/

I think there might have been a little talk about better solutions for
file-hosting that might address some of these problems, but I'm not
aware of any serious work being done.

Rich