Apparently, though unproven, at 22:10 on Thursday 18 November 2010, Mick did opine thusly:
> I have installed E17 using layman and the efl overlay, but today I just ran > dispatch-conf and these changes showed up: > ========================================= > --- /etc/portage/package.use 2010-11-15 12:50:46.000000000 +0000 > +++ /etc/portage/._cfg0000_package.use 2010-11-18 19:35:35.000000000 +0000 > @@ -8,11 +8,11 @@ > net-wireless/bluez gstreamer pcmcia > app-portage/layman subversion > #entrance > -x11-libs/evas X jpeg png svg xpm > -x11-libs/ecore X curl > +media-libs/evas X jpeg png svg xpm > +dev-libs/ecore X curl > #E17 > -x11-libs/e_dbus X > -x11-libs/evas X jpeg png svg xpm fontconfig > +dev-libs/e_dbus X > +media-libs/evas X jpeg png svg xpm fontconfig > #efl overlay > dev-libs/ecore glib threads xim curl ssl inotify evas opengl X xinerama > xprint xscreensaver -sdl -gnutls > dev-libs/eet ssl threads -gnutls > > >> (1 of 1) -- /etc/portage/package.use > >> q quit, h help, n next, e edit-new, z zap-new, u use-new > > m merge, t toggle-merge, l look-merge: > ========================================= > > Why is this? Do I want to accept these changes? I am not sure if they are > caused by layman or portage proper. You have a mixture of vapier's overlay from layman and barberi's overlay from enlightenment.org, evas and ecore changed category from x11-libs to dev-libs in barberi's overlay. You can't have both, they conflict. Do this: delete the vapier overlay - it's WAAAAAAAAAAAAY outdated accept conf-update changes related to e17 install the efl overlay from enlightenment.org - it's currently maintained delete any and all e17 packages. emerge @e17 keep in mind for the future that you can't update the e17 packages why they are at version 9999. You must update the entire lot, in order, anytime you want to update anything. This is normal for -9999 packages -- alan dot mckinnon at gmail dot com
