Wulf C. Krueger wrote:

> For quite some time now, our progress has been impaired by the absence of
> features like USE dependencies, ranged dependencies and suggested
> dependencies.
>
How do suggested dependencies help in your work?

> Most of us who are working on the overlay have been using alternative
> package managers (PM) for quite some time now. Thus, the idea arose to go
> a step further and actually make good use of the capabilities they offer
> us.
>
Makes sense; after all you can do whatever you want in an overlay without
concern for how it will affect anyone else.
 
> You'll find all the details in the following local copy of PMS with the
> kdebuild-1 patch applied: http://www.mailstation.de/pms.pdf
> 
Thanks, I'll have a closer look when I get some downtime.

> For starters, we'll be using the new EAPI for live ebuilds (${PV}=-scm)
> only, so that users of other PMs will be able to use the rest of the
> overlay as before. That's exactly what the kdebuild-1 EAPI was designed
> to allow for.
> 
> For users of the KDE overlay's live ebuilds the new EAPI currently means
> they will have to use Paludis but there are rumours ;) other PMs are
> interested as well. That's the main reason to optionally include it in
> PMS.
> 
Could you explain exactly what -scm-foo offers over the existing -cvs
implementation? I'm assuming it's something more than what you've outlined
here.

A bit more info on how the other features have helped would be nice (maybe a
GMN article?)

Thanks.


-- 
gentoo-dev@g.o mailing list