public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fw: [gentoo-commits] gentoo-x86 commit in app-backup/bacula: bacula-5.0.2-r2.ebuild ChangeLog
Date: Fri, 23 Jul 2010 12:37:56 +0100	[thread overview]
Message-ID: <20100723123756.6d2e587b@snowcone> (raw)
In-Reply-To: <20100723133002.7912f158@test>

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

On Fri, 23 Jul 2010 13:30:02 +0200
Thomas Beierlein <tomjbe@gentoo.org> wrote:
> > > interesting. I did not know that an ebuild can use-depend on
> > > itself. Good to know.
> >
> > No, not good. It doesn't make any sense.
> 
> Can you give some reasoning for that?

It's entirely unclear what deps upon self actually mean. Some people
use them to say that a package needs to be installed before it can
install itself. Thus, things like:

    DEPEND="|| ( myself myself-bin )"

So a dependency upon myself[foo] would probably mean "I need
myself[foo] to be installed before I can install myself", not "I need
the foo flag to be set on myself".

In any case, abusing DEPEND isn't a mechanism for implementing use
requirements. You should use the mechanism that's designed for use
requirements to do use requirements, which means waiting for EAPI 4
and pkg_pretend, or just follow existing policy and pick one in the
case of a conflict.

- -- 
Ciaran McCreesh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEARECAAYFAkxJfxcACgkQ96zL6DUtXhGXkQCcDzxMWkqm+ShdOEBOWH0nQJtE
q0gAn0TRU7BtLVyKib6YJLNWtjjWoNFk
=uYQb
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-07-23 11:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 16:20 [gentoo-dev] Fw: [gentoo-commits] gentoo-x86 commit in app-backup/bacula: bacula-5.0.2-r2.ebuild ChangeLog Thomas Beierlein
2010-07-22 18:04 ` Jorge Manuel B. S. Vicetto
2010-07-23  7:06   ` Thomas Beierlein
2010-07-23  8:38     ` Tomáš Chvátal
2010-07-23 12:10       ` Thomas Beierlein
2010-07-23  9:31     ` Tiziano Müller
2010-07-23 11:30       ` Thomas Beierlein
2010-07-23 11:37         ` Ciaran McCreesh [this message]
2010-07-23 12:30           ` Jorge Manuel B. S. Vicetto
2010-07-23 12:39             ` Ciaran McCreesh
2010-07-23 12:28       ` Jorge Manuel B. S. Vicetto
2010-07-23 12:43         ` Ciaran McCreesh

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=20100723123756.6d2e587b@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-dev@lists.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