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.43)
	id 1EGJib-0005oW-9j
	for garchives@archives.gentoo.org; Fri, 16 Sep 2005 17:09:45 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
	by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j8GH3vk3014341;
	Fri, 16 Sep 2005 17:03:57 GMT
Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204])
	by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j8GH2BwP023395
	for <gentoo-dev@lists.gentoo.org>; Fri, 16 Sep 2005 17:02:12 GMT
Received: by zproxy.gmail.com with SMTP id x7so547648nzc
        for <gentoo-dev@lists.gentoo.org>; Fri, 16 Sep 2005 10:07:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id:sender;
        b=sluHiFdKNe4qoU0FvJpTI+kU2VPs8Iu4RDH9Xbgq3SyJTl61F6D9BC5WqHwgHi75AH9H1L+Kjvqs74BhLF0eHjnKwUdKfeFvgUlwfLXf0UyQ5cI/BOHgFA5P8U6FJ+jzzZrrCGlPRpIHqhsTi03a4EpexFL0BJHRXR993ItHeNc=
Received: by 10.54.138.2 with SMTP id l2mr252546wrd;
        Fri, 16 Sep 2005 10:07:18 -0700 (PDT)
Received: from ?192.168.0.2? ( [151.56.16.118])
        by mx.gmail.com with ESMTP id 12sm548413wrl.2005.09.16.10.07.16;
        Fri, 16 Sep 2005 10:07:18 -0700 (PDT)
From: "Diego 'Flameeyes' =?utf-8?q?Petten=C3=B2?=" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Portability eclass
Date: Fri, 16 Sep 2005 19:07:00 +0200
User-Agent: KMail/1.8.2
References: <200509161743.07528@enterprise.flameeyes.is-a-geek.org> <1126887370.5006.91.camel@lycan.lan>
In-Reply-To: <1126887370.5006.91.camel@lycan.lan>
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: multipart/signed;
  boundary="nextPart1752984.fIToHVTMqj";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200509161907.11231@enterprise.flameeyes.is-a-geek.org>
Sender: "=?UTF-8?Q?Diego=20\"Flameeyes\"=20Petten=C3=B2?=" <flameeyes@gmail.com>
X-Archives-Salt: cf476539-0710-4f64-a1f2-762e5d2a38c3
X-Archives-Hash: d9ccee0ebee47497e27fa23ecd5535e9

--nextPart1752984.fIToHVTMqj
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 16 September 2005 18:16, Martin Schlemmer wrote:
> I do not think its so urgent? =C2=A0Either way, we have elibs approved no=
w,
> so how about waiting a while so that we do not have yet another elib
> candidate to port?
There are at least two ebuilds in portage that uses cp --parente . It wasn'=
t=20
being a problem if it wasn't used.

elib can be approved, but we're working on Gentoo/*BSD (and Gentoo/OSX) now=
,=20
not 4 years from now (ok that was an exageration, but simplify what the=20
problem is: it doesn't seem probable that a newer portage goes out working=
=20
and ebuilds start using the new features in a little time.

Remember that we had a bit of opposition also to have gcc using USE_EXPAND-=
ed=20
variables, I can't figure what would happen also if tomorrow we find a=20
portage with elib working :/

=2D-=20
Diego "Flameeyes" Petten=C3=B2
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)

--nextPart1752984.fIToHVTMqj
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDKvu/e2h1+2mHVWMRAjgcAJwOsQcS79XlwbLWqYuys4vnXPss1ACZAYts
qEvgYMz2rc0lGmp7QNKqOwc=
=pAP4
-----END PGP SIGNATURE-----

--nextPart1752984.fIToHVTMqj--
-- 
gentoo-dev@gentoo.org mailing list