| 1 |
Hi, |
| 2 |
|
| 3 |
Josh Saddler <nightmorph@g.o>: |
| 4 |
|
| 5 |
> Tiziano Müller wrote: |
| 6 |
> > Hi everyone |
| 7 |
> > |
| 8 |
> > With eapis 1 and 2 we introduced nice features but also a couple of |
| 9 |
> > new problems. One of them are the use dependencies when the package |
| 10 |
> > you depend on doesn't have the use flag anymore (see [1] for an |
| 11 |
> > example). |
| 12 |
> > |
| 13 |
> > So I think it's time for a short eapi bump with some distinct |
| 14 |
> > improvements: |
| 15 |
> > |
| 16 |
> > http://spreadsheets.google.com/ccc?key=pPAJXP6shYH78lCXeqRqCUQ |
| 17 |
> |
| 18 |
> Is there a reason why we should ram through a new EAPI for something |
| 19 |
> that *looks* like another "Paludis supports this so let's make it a |
| 20 |
> Portage standard" proposal? Is there some kind of time deadline here |
| 21 |
> that you all want? |
| 22 |
|
| 23 |
built_with_use supports exactly that with the --missing switch and |
| 24 |
yesterday I noticed some ebuilds that could not be transferred to |
| 25 |
EAPI 2 because of that. |
| 26 |
|
| 27 |
> Also, why the bannination of || ( foo? (.).) -- how is it error prone, |
| 28 |
> exactly. |
| 29 |
|
| 30 |
I would like to hear about that, too. |
| 31 |
|
| 32 |
V-Li |
| 33 |
|
| 34 |
-- |
| 35 |
Christian Faulhammer, Gentoo Lisp project |
| 36 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
| 37 |
|
| 38 |
<URL:http://www.faulhammer.org/> |
Archives