public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org,
	"Martin Schlemmer" <azarah@gentoo.org>,
	"Diego Pettenò" <flameeyes@gentoo.org>
Subject: Re: [gentoo-dev] autotools.eclass and binary packages
Date: Sat, 05 Aug 2006 14:29:57 -0700	[thread overview]
Message-ID: <44D50DD5.9040307@gentoo.org> (raw)
In-Reply-To: <200608051608.40344.vapier@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Frysinger wrote:
> On Saturday 05 August 2006 15:32, Zac Medico wrote:
>> The actual fault is in libpng-1.2.12-r1.ebuild where RDEPEND="" should be
>> explicitly set.
> 
> the actual fault is portage
> 
> instead of half-assing all this DEPEND/RDEPEND garbage, why not fix portage to 
> do it consistently
> 
> either it implicitly sets RDEPEND *correctly* or it doesnt do it at all
> -mike

I'm not satisfied with the current implicit RDEPEND behavior either.  I propose that we make repoman force explicit definition of RDEPEND.  After all of the ebuilds have been fixed to stop relying on the implicit definition, we can fix portage so that it no longer sets RDEPEND implicitly at all.

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

iD8DBQFE1Q3R/ejvha5XGaMRAsfPAJ995BeuHN7oCUnaaKmTsijGIHd0zQCfUErR
1z101NNdxc2VpH08BoMZsJo=
=L2kn
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-05 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05 14:12 [gentoo-dev] autotools.eclass and binary packages Christian Heim
2006-08-05 18:37 ` Mike Frysinger
2006-08-05 19:32 ` Zac Medico
2006-08-05 20:08   ` Mike Frysinger
2006-08-05 21:29     ` Zac Medico [this message]
2006-08-05 22:26       ` [gentoo-dev] implicit RDEPEND Mike Frysinger
2006-08-06  0:02         ` Zac Medico
2006-08-07 17:36         ` Carsten Lohrke
2006-08-07 23:25           ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44D50DD5.9040307@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=azarah@gentoo.org \
    --cc=flameeyes@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox