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 201A2138A1F for ; Wed, 29 Jan 2014 22:56:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EACBCE0C0A; Wed, 29 Jan 2014 22:53:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 19BA2E0C03 for ; Wed, 29 Jan 2014 22:53:21 +0000 (UTC) Received: from [IPv6:2a01:e34:ee10:4dc0:922b:34ff:fe30:2648] (unknown [IPv6:2a01:e34:ee10:4dc0:922b:34ff:fe30:2648]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: eva) by smtp.gentoo.org (Postfix) with ESMTPSA id B75DA33F343 for ; Wed, 29 Jan 2014 22:53:19 +0000 (UTC) Message-ID: <1391035996.29447.0.camel@kanae> Subject: Re: [gentoo-dev] Re: Dealing with XDG directories in ebuild environment From: Gilles Dartiguelongue To: gentoo-dev@lists.gentoo.org Date: Wed, 29 Jan 2014 23:53:16 +0100 In-Reply-To: <20140128131120.GA2084@rathaus.eclipse.co.uk> References: <20140125221628.26f3aa96@pomiot.lan> <20140126204926.33f2baef@googlemail.com> <20140128131120.GA2084@rathaus.eclipse.co.uk> Organization: Gentoo Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.3 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 Content-Transfer-Encoding: 8bit X-Archives-Salt: 08529d57-44c4-4dc3-a7f0-77a4e76105f7 X-Archives-Hash: 17d0a8c518a4311ddf9fca09fb80944f Le mardi 28 janvier 2014 à 13:11 +0000, Steven J. Long a écrit : > Alec Warner wrote: > > Sorry, I work on Portage. What I'm saying is that We are free to change the > > behavior of *portage* now; rather than waiting for a new EAPI. If an ebuild > > needs to define EAPI=eapi-next to 'correctly' use XDG_*, well that is > > someone else's can of worms. > > Agreed: portage can clear those vars from the env as mgorny stated on the bug, > and an xdg.eclass (or w/e) can setup good defaults for packages which need > them. Presumably it'd be inherited by gnome and kde eclasses, for example, > so most people wouldn't even see it. Exactly. -- Gilles Dartiguelongue Gentoo