On Wed, 05 Sep 2012 00:06:45 +0000 "Jorge Manuel B. S. Vicetto" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 31-08-2012 20:46, Ciaran McCreesh wrote: > > > > > Also, we're getting rather a lot of *DEPEND variables here... If > > we're making people make major changes to their deps, which for > > HDEPEND we definitely would be, then the "it's expensive since > > people would have to redo their deps" argument against a combined > > DEPENDENCIES variable goes out of the window, so we should rethink > > that too. > > I have to agree with Ciaran, instead of multiplying DEPEND variables, > it's probably time we move to a single DEPENDENCIES variable. Well, if you really insist that Gentoo is the right place to reinvent the wheel of bash variables... If we really want to go this route, then please at least require explicit label at start of DEPENDENCIES. And the same when appending to DEPENDENCIES -- just so 'unlikely' mistakes will leave us with hours of debugging. Furthermore, please think of eclasses. They *all* will have to append dependencies in two ways, in an EAPI-conditional way. Exherbo doesn't have that problem because they don't care about backwards compatibility. We will support old EAPIs for at least few years if not until the end of Gentoo. Not that appending dependencies in eclasses is really that good idea. Remember that this requirement will actually cause migration to EAPI 5 to be even harder than to any previous EAPIs. Migrating a single ebuild will require rewriting the dependencies, and migrating an eclass will require adding a lot of dirty code. Especially if it is python.eclass. And we will have to convert them back to old-style dependencies anyway. For the sake of compatibility with external tools. And as a final note, on a request from ulm, I have created a wiki page where you could list all proposed new dependency types so we can have a broader look when deciding: http://wiki.gentoo.org/wiki/Future_EAPI/New_dependency_types -- Best regards, Michał Górny