From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.62)
(envelope-from <gentoo-dev+bounces-24802-garchives=archives.gentoo.org@gentoo.org>)
id 1I7PZr-0004dr-1y
for garchives@archives.gentoo.org; Sun, 08 Jul 2007 05:44:59 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l685hvmN014854;
Sun, 8 Jul 2007 05:43:57 GMT
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228])
by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l685g2wS012544
for <gentoo-dev@lists.gentoo.org>; Sun, 8 Jul 2007 05:42:02 GMT
Received: by wx-out-0506.google.com with SMTP id h30so1068131wxd
for <gentoo-dev@lists.gentoo.org>; Sat, 07 Jul 2007 22:42:02 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
d=gmail.com; s=beta;
h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=QJN/vtfPuH3giaN3XXKeshERymmmKwDw0AUgjyggnYItD1iep7lPNaiWpMP6H9OLWXVsOX1I1FRvRcmpVt3eLlzJ15GguVqHr8RmUbYE/dZA/R9F1xMSMjuuO5vgEyXluQcrMQe6NnB5oVqfa/umNU9kn/5F4FOVPbGepDRWuss=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
b=GVnRLl7bUGwut4QR9upRbhweye3n+SviXH2Wo9q5qYT5942QnigyXiphfe5ibfIN1FbPFdT7yumx+C/D78qnMioxrBO+UGlNSGIn4wHSOY1l8K5Bp8M0HN9cHUr8PxXpKc/LvS+p35Ad2jBYO1P58fKobRtaoXl0T8T3pZGzUhg=
Received: by 10.90.83.14 with SMTP id g14mr1174775agb.1183873322296;
Sat, 07 Jul 2007 22:42:02 -0700 (PDT)
Received: by 10.90.51.6 with HTTP; Sat, 7 Jul 2007 22:42:02 -0700 (PDT)
Message-ID: <d14bee470707072242s33e4434bl83fd53d7a9a5e165@mail.gmail.com>
Date: Sun, 8 Jul 2007 00:42:02 -0500
From: "Alex Tarkovsky" <alextarkovsky@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: John Jawed & Alex Tarkovsky's einput eclass
In-Reply-To: <f6pn1i$963$1@sea.gmane.org>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f62u7q$b7q$1@sea.gmane.org> <468F85BC.9060102@gentoo.org>
<f6pn1i$963$1@sea.gmane.org>
X-Archives-Salt: 0aff7d63-87c2-41df-bbcc-51ae58f29fb0
X-Archives-Hash: d5e8a42df2871b24b3ec36485abc2eab
On 7/7/07, Steve Long <slong@rathaus.eclipse.co.uk> wrote:
> I'm ofc not including fetch-restricted which also require interaction,
> although that is standardised enough for a script to deal with[1]. Having
> found this for games, I can deal with that too ofc, but I still think the
I'm not sure whether special license agreements are a legitimate case
for interactivity in some ebuilds, but I can tell you the einput
eclass was intended to be used only in pkg_config(), meaning the only
time the user would ever encounter einput is when they specifically
run "emerge --config foo" after installation, and even then it would
be only in a handful of ebuilds that actually need einput's services.
Burdening the user with the prospect of interactivity in any other
ebuild phase does seem to go against the Portage philosophy, so I feel
that einput.eclass is an edge case tool at best.
--
gentoo-dev@gentoo.org mailing list