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 2438F138247 for ; Thu, 2 Jan 2014 14:02:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AA868E0AFD; Thu, 2 Jan 2014 14:01:57 +0000 (UTC) Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CF31DE0A64 for ; Thu, 2 Jan 2014 14:01:56 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id w7so13662135qcr.11 for ; Thu, 02 Jan 2014 06:01:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=q4E60uR95K5l968lg0CFu3jujbpWX1S7sxeruTS6UgM=; b=uuCLczjShfKnwwftLc+S8BQ4IelA8p4pZ6HIiOVqDmWu7FgE6q5wHu3FvlRGXJTRzW soSrQ6W5ehyWU0Ts42LgTy/sSBDzT3x1dYiSAVuBl1n6HBoSoioAIPmtFDowKoNMt9qd tyBq/VyS7goipbexho1JGhWMMfsv/qZuIrjVRWpeB6GKjtjINSYEQqfHqPkNIEApQZVH 3SxxUfCduCkh1Yy2vqbgfqVFOt/6iVgSCIuzDFacL9lJstrgKaQLKT+fFkUZzeTyxREY CuDZLsmoiGku5IpFhq1k2rI+XKh1h2sloLJ0oHi8+df/Ifl/qxNaQlv1PZXNiJNFDlSe iTkQ== 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 X-Received: by 10.224.115.70 with SMTP id h6mr138878533qaq.61.1388671316050; Thu, 02 Jan 2014 06:01:56 -0800 (PST) Received: by 10.140.93.230 with HTTP; Thu, 2 Jan 2014 06:01:55 -0800 (PST) In-Reply-To: <20140102065006.59a2bad9@caribou.gateway.pace.com> References: <21188.38566.180273.751353@a1i15.kph.uni-mainz.de> <20140102065006.59a2bad9@caribou.gateway.pace.com> Date: Fri, 3 Jan 2014 03:01:55 +1300 Message-ID: Subject: Re: [gentoo-dev] Re: RFC: new global USE flag "srcdist" From: Kent Fredric To: gentoo-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary=047d7bf1600680c4b304eefd3cb8 X-Archives-Salt: b489e445-e181-424a-ab88-7be0fe3dcff4 X-Archives-Hash: 191b60333c83687026694db8f8d5bf83 --047d7bf1600680c4b304eefd3cb8 Content-Type: text/plain; charset=UTF-8 On 3 January 2014 01:50, Ryan Hill wrote: > Maybe we could add RESTRICT=srcdist which would cause ebuilds to save > their distfiles in a separate directory controlled by PORTDIR_NODIST or > something. If the variable is unset then it's business as usual. > I was going to suggest similar. Though I hadn't thought about it at a global RESTRICT level, but I had envisioned that potentially, the redistribubility should be a property of a source file, not of en ebuild. For example, if there was something such as java, which would likely be mirror-restricted, it the java binaries themselves would be mirror restricted. However, if there were any tools/patches provided by gentoo and also in src_uri, marking them as no-mirror seems counter productive. Just the RESTRICT based interface seems more obvious, where as spicing SRC_URI values properly could be nuanced and complicated. -- Kent --047d7bf1600680c4b304eefd3cb8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 3 January 2014 01:50, Ryan Hill <dirtyepic@gentoo.org>= wrote:
M= aybe we could add RESTRICT=3Dsrcdist which would cause ebuilds to save
their distfiles in a separate directory controlled by PORTDIR_NODIST or
something. =C2=A0If the variable is unset then it's business as usual.<= /div>

I was going to= suggest similar.

Though I hadn'= ;t thought about it at a global RESTRICT level, but I had envisioned that p= otentially, the redistribubility should be a property of a source file, not= of en ebuild.

For example, if there was something su= ch as java, which would likely be mirror-restricted,=C2=A0 it the java bina= ries themselves would be mirror restricted.

However, if there were a= ny tools/patches provided by gentoo and also in src_uri, marking them as no= -mirror seems counter productive.

Just the RESTRICT based interfac= e seems more obvious, where as spicing SRC_URI values properly could be nua= nced and complicated.

=

--
Kent
--047d7bf1600680c4b304eefd3cb8--