From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-dev+bounces-29874-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1JZwaU-0006Ob-9D
	for garchives@archives.gentoo.org; Thu, 13 Mar 2008 23:11:50 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id A4267E09B0;
	Thu, 13 Mar 2008 23:11:48 +0000 (UTC)
Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224])
	by pigeon.gentoo.org (Postfix) with ESMTP id 828D1E09B0
	for <gentoo-dev@lists.gentoo.org>; Thu, 13 Mar 2008 23:11:48 +0000 (UTC)
Received: by wr-out-0506.google.com with SMTP id c48so2970893wra.1
        for <gentoo-dev@lists.gentoo.org>; Thu, 13 Mar 2008 16:11:48 -0700 (PDT)
Received: by 10.114.126.1 with SMTP id y1mr10535071wac.108.1205449907413;
        Thu, 13 Mar 2008 16:11:47 -0700 (PDT)
Received: by 10.115.15.6 with HTTP; Thu, 13 Mar 2008 16:11:47 -0700 (PDT)
Message-ID: <430880c50803131611j5df68da4u33284268acdc9160@mail.gmail.com>
Date: Fri, 14 Mar 2008 00:11:47 +0100
From: "Fabio Erculiani" <lxnay@sabayonlinux.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Help offered - Portage tree
In-Reply-To: <47D9B2F6.4080900@gentoo.org>
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
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <430880c50803121635g294f505av259707f7e6a746bb@mail.gmail.com>
	 <47D9AA29.8070303@gentoo.org>
	 <430880c50803131542v1e72eb75k44c24161469e148b@mail.gmail.com>
	 <47D9B2F6.4080900@gentoo.org>
X-Archives-Salt: f94e2b76-5118-4320-9f04-b4d1c73aa687
X-Archives-Hash: 82502d26cc8a4da030bbe54fb94f7c91

Joshua,
I know that draft quite well, I used as reference for writing Entropy,
our binary package manager which only uses {R,P}DEPEND and not DEPEND.
So here comes the issue, when *DEPEND are not declared properly
Entropy pulls in unneeded packaged.
What you are saying is something I am already aware of :) zmedico has
been really helpful :)

On 3/14/08, joshua jackson <tsunam@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>  Fabio Erculiani wrote:
>
> | Hi Joshua,
>  | I never had issues with my emails. So I don't really know what to
>  | answer you regarding to your issues :)
>  | SPLIT: Although I think it can be a suboptimal thing for us, I can
>  | understand your policy. Let me add that, to me, the biggest issue is
>  | about (R)DEPEND. Splitting packages and maintaining in an overlay it's
>  | not that hard.
>  |
>  |
>  |
>
> I personally have no desire to follow the redhat/debian/other binary
>  packaging systems which split up infinitesimally small packages. It
>  causes a lot more busywork in my opinion then any potential benefits
>  that it gains you.
>
>  As far as the depend issue you mentioned: Having both Rdepends and
>  Depends isn't as far as I'm aware part of any EAPI currently (Correct me
>  if I'm wrong people). Rdepends are needed for the builds so you will
>  often see either RDEPENDS=${DEPEND} or vice versa. If its not there then
>  its more of a matter of accounting then anything. I would think, and
>  correct me if I'm wrong again, that it would make sense that if you only
>  have RDEPENDS or DEPEND, then those same applications are required in
>  the runtime of the application. Does it need to be explicitly stated? So
>  far the three package manager that I'm aware of all manage this fine.
>  Those being portage, paludis, and pkgcore. If there are other package
>  managers out there that might have issues Its a perfect example of a
>  reason to be involved in the EAPI discussions to help define what is
>  needed and where.
>
>  So what I suggest to you is perhaps looking over the EAPI=0 draft
>  documentation and proposing some additions and or modifications that
>  benefit everyone (not just one person), as its designed to be a standard
>  for anyone who makes use of ebuilds and beyond.
>
>  http://dev.gentoo.org/~spb/pms.pdf
>
>  Is the current form, but halcy0n is working on an updated version of it
>  for the next council meeting.
>
> -----BEGIN PGP SIGNATURE-----
>  Version: GnuPG v2.0.7 (GNU/Linux)
>  Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
>
> iD8DBQFH2bL22ZWR0Jhg/EsRAkduAJsGBKKl5HgR5YXziPn9yOLbi5F5MwCfacIC
>  b/aqsokP3A6JFJ7hO4LGNXY=
>  =BGqi
>
> -----END PGP SIGNATURE-----
>  --
>  gentoo-dev@lists.gentoo.org mailing list
>
>


-- 
Fabio Erculiani
Information and Communication Technologies Consultant
Sabayon Linux Chief Architect
http://www.sabayonlinux.org
-- 
gentoo-dev@lists.gentoo.org mailing list