Gentoo Archives: gentoo-dev

From: Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>
To: gentoo-dev@l.g.o
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 11:38:21
Message-Id: 20100723123756.6d2e587b@snowcone
In Reply to: Re: [gentoo-dev] Fw: [gentoo-commits] gentoo-x86 commit in app-backup/bacula: bacula-5.0.2-r2.ebuild ChangeLog by Thomas Beierlein
Hash: SHA1

On Fri, 23 Jul 2010 13:30:02 +0200
Thomas Beierlein <tomjbe@g.o> 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-----