| 1 |
On Tuesday 15 March 2011 21:47:28 Alan McKinnon wrote: |
| 2 |
> On 15/03/11 22:54, Ian Lee wrote: |
| 3 |
> > On 15/03/11 19:15, Mick wrote: |
| 4 |
> >> I'm trying to emerge the latest dev-libs/efreet-9999, but it fails as |
| 5 |
> >> shown below: |
| 6 |
[snip ...] |
| 7 |
|
| 8 |
> >> Any ideas? |
| 9 |
> >> |
| 10 |
> > Update Ecore. |
| 11 |
> |
| 12 |
> Further to that, efl-9999 is not stable and changes to the code are not |
| 13 |
> reflected in version number bumps. It's all in svn so who knows what |
| 14 |
> you'll get on any given day. From long bitter hard experience: |
| 15 |
> |
| 16 |
> Just write a little script that rebuilds ALL of efl anytime you want to |
| 17 |
> rebuild any part of it. Do not be tempted to short cut this process, too |
| 18 |
> often it ends in tears. Just bite the bullet and let it run. |
| 19 |
> |
| 20 |
> Creating a portage set with all efl & e17 ebuilds in it also works. Then |
| 21 |
> you can "emerge @e17" and get the same result as a wrapper script. |
| 22 |
|
| 23 |
Ah! Yes, I used to have a little script but lost it when I rebuilt the |
| 24 |
machine following a fs corruption. How can I find now all the e17 packages I |
| 25 |
have emerged? |
| 26 |
-- |
| 27 |
Regards, |
| 28 |
Mick |
Archives