Re: [gentoo-user] E17 and package.use
On Thursday 18 November 2010 22:41:49 Alan McKinnon wrote: With all these changes it's hard to give firm advice, except to say this: If conf-update wants to make changes to package categories, and eix on your machine gives the same new ones as the new config file, then make the change. Otherwise find out why you are out of step. Yep, eix is telling me that suggested changes are sane and therefore I should accept them. having said that, yes it does look like you have enlightenment overlay uninstalled and the efl one installed. And it looks like you are now going to switch them back around again. Life on the bleeding edge is fun, right? Fun but uncomfortable! = Calculating dependencies... done! !!! All ebuilds that could satisfy dev-libs/e_dbus have been masked. !!! One of the following masked packages is required to complete your request: - dev-libs/e_dbus-1.0.0_beta2 (masked by: ~amd64 keyword) = So it seems that I should delete efl, install enlightenment overlay instead, remove any package.keywords on all ** packages (?) that I had set up for efl and instead unmask beta versions of packages as portage is telling me to do. Have I got this right, or should I leave ** in my package keywords for the enlightenment packages? I may wait until Sunday or so in the hope that all this dust has settled, because I fear that I may be caught half-way between changes on efl and enlightenment overlays with no way of installing a working desktop. Thanks again for holding my hand on this. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] E17 and package.use
Apparently, though unproven, at 11:06 on Friday 19 November 2010, Mick did opine thusly: On Thursday 18 November 2010 22:41:49 Alan McKinnon wrote: With all these changes it's hard to give firm advice, except to say this: If conf-update wants to make changes to package categories, and eix on your machine gives the same new ones as the new config file, then make the change. Otherwise find out why you are out of step. Yep, eix is telling me that suggested changes are sane and therefore I should accept them. having said that, yes it does look like you have enlightenment overlay uninstalled and the efl one installed. And it looks like you are now going to switch them back around again. Life on the bleeding edge is fun, right? Fun but uncomfortable! = Calculating dependencies... done! !!! All ebuilds that could satisfy dev-libs/e_dbus have been masked. !!! One of the following masked packages is required to complete your request: - dev-libs/e_dbus-1.0.0_beta2 (masked by: ~amd64 keyword) = So it seems that I should delete efl, install enlightenment overlay instead, remove any package.keywords on all ** packages (?) that I had set up for efl and instead unmask beta versions of packages as portage is telling me to do. Have I got this right, or should I leave ** in my package keywords for the enlightenment packages? You shouldn't have to unmask the packages as they won't be listed in profiles/package.mask, so the keyword method should be right. And we'll have to watch for category/package names changes as well and modify keywords to suit. But that won't break anything, you'll get a message saying a package is masked. Once you unmask/keyword it, the emerge will proceed. I may wait until Sunday or so in the hope that all this dust has settled, because I fear that I may be caught half-way between changes on efl and enlightenment overlays with no way of installing a working desktop. Thanks again for holding my hand on this. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] E17 and package.use
Apparently, though unproven, at 11:06 on Friday 19 November 2010, Mick did opine thusly: So it seems that I should delete efl, install enlightenment overlay instead, remove any package.keywords on all ** packages (?) that I had set up for efl and instead unmask beta versions of packages as portage is telling me to do. Have I got this right, or should I leave ** in my package keywords for the enlightenment packages? I may wait until Sunday or so in the hope that all this dust has settled, because I fear that I may be caught half-way between changes on efl and enlightenment overlays with no way of installing a working desktop. Thanks again for holding my hand on this. It just got even more interesting. The EFL libs (but not the window manager) just got committed to the portage tree. The version is 1.0.0_beta2 and the devs have stated they intend no more API/ABI breakages. So I'm tempted to say we should install the beta libs so we don't have to constantly upgrade the whole lot. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] E17 and package.use
On Friday 19 November 2010 23:14:01 Alan McKinnon wrote: Apparently, though unproven, at 11:06 on Friday 19 November 2010, Mick did opine thusly: So it seems that I should delete efl, install enlightenment overlay instead, remove any package.keywords on all ** packages (?) that I had set up for efl and instead unmask beta versions of packages as portage is telling me to do. Have I got this right, or should I leave ** in my package keywords for the enlightenment packages? I may wait until Sunday or so in the hope that all this dust has settled, because I fear that I may be caught half-way between changes on efl and enlightenment overlays with no way of installing a working desktop. Thanks again for holding my hand on this. It just got even more interesting. The EFL libs (but not the window manager) just got committed to the portage tree. The version is 1.0.0_beta2 and the devs have stated they intend no more API/ABI breakages. So I'm tempted to say we should install the beta libs so we don't have to constantly upgrade the whole lot. Excellent! It's getting late over here, so I'll get on with this tomorrow. -_- For x11-wm/enlightenment I'll have to keep ** in keywords, but switch overlay to 'enlightenment'. Is the efl overlay going to be taken offline in the future? PS. I'm impressed, but where do you go to find all this info about enlightenment gentoo? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] E17 and package.use
Apparently, though unproven, at 01:31 on Saturday 20 November 2010, Mick did opine thusly: For x11-wm/enlightenment I'll have to keep ** in keywords, but switch overlay to 'enlightenment'. Add the enlightenment overlay, but read a few key ebuilds to get a grasp of what's going on and what they want Is the efl overlay going to be taken offline in the future? I think so, but that's me reading between the lines. It seems to be an experimental test bed, sort of like how the kde overlay gets used PS. I'm impressed, but where do you go to find all this info about enlightenment gentoo? Been using e17 for years :-) I subscribe to the e17 commit list and read all the various blogs etc, etc. Plus read all the numerous eclasses that have been around over the years and even maintained my own ebuilds for a while till barbeiri released his. After all that, I guess some of the info made it into long-term memory :-) -- alan dot mckinnon at gmail dot com
[gentoo-user] E17 and package.use
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.use2010-11-15 12:50:46.0 + +++ /etc/portage/._cfg_package.use 2010-11-18 19:35:35.0 + @@ -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. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] E17 and package.use
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.use2010-11-15 12:50:46.0 + +++ /etc/portage/._cfg_package.use 2010-11-18 19:35:35.0 + @@ -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 WY 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 . You must update the entire lot, in order, anytime you want to update anything. This is normal for - packages -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] E17 and package.use
On Thursday 18 November 2010 20:26:36 Alan McKinnon wrote: 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.use2010-11-15 12:50:46.0 + +++ /etc/portage/._cfg_package.use 2010-11-18 19:35:35.0 + @@ -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 WY 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 . You must update the entire lot, in order, anytime you want to update anything. This is normal for - packages Thank you Alan, I seem to recall that at one point I did try Vapier's overlay, but it didn't work and then you kindly suggested that I used this: $ layman -l * efl [Subversion] (http://svn.enlightenment.org/svn/e/trunk/packaging/gentoo Now, when I try to delete vapier's I get this: # layman -d enlightenment * Overlay enlightenment does not exist. Am I right then to assume that it is no longer installed? $ ls -la /var/lib/layman/ total 158 drwxr-xr-x 3 root root 8 Nov 1 20:10 . drwxr-xr-x 32 root root 36 Nov 18 19:14 .. -rw-r--r-- 1 root root 154200 Nov 18 21:21 cache_ac494f50f5736be7871962c0dec7b3bb.xml -rw-r--r-- 1 root root379 Nov 18 21:06 cache_f4870c06236b316a7c7915b9c5fa4960.xml drwxr-xr-x 20 root root 21 Nov 18 20:08 efl -rw-r--r-- 1 root root 0 Nov 1 20:10 .keep_app-portage_layman-0 -rw-r--r-- 1 root root 57 Jun 11 07:23 make.conf -rw-r--r-- 1 root root480 Jun 11 07:23 overlays.xml So I *should* be safe to accept the changes that dispatch-conf suggests, right? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] E17 and package.use
Apparently, though unproven, at 00:04 on Friday 19 November 2010, Mick did opine thusly: On Thursday 18 November 2010 20:26:36 Alan McKinnon wrote: 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.use2010-11-15 12:50:46.0 + +++ /etc/portage/._cfg_package.use 2010-11-18 19:35:35.0 + @@ -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 WY 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 . You must update the entire lot, in order, anytime you want to update anything. This is normal for - packages Thank you Alan, I seem to recall that at one point I did try Vapier's overlay, but it didn't work and then you kindly suggested that I used this: $ layman -l * efl [Subversion] (http://svn.enlightenment.org/svn/e/trunk/packaging/gentoo Now, when I try to delete vapier's I get this: # layman -d enlightenment * Overlay enlightenment does not exist. Am I right then to assume that it is no longer installed? $ ls -la /var/lib/layman/ total 158 drwxr-xr-x 3 root root 8 Nov 1 20:10 . drwxr-xr-x 32 root root 36 Nov 18 19:14 .. -rw-r--r-- 1 root root 154200 Nov 18 21:21 cache_ac494f50f5736be7871962c0dec7b3bb.xml -rw-r--r-- 1 root root379 Nov 18 21:06 cache_f4870c06236b316a7c7915b9c5fa4960.xml drwxr-xr-x 20 root root 21 Nov 18 20:08 efl -rw-r--r-- 1 root root 0 Nov 1 20:10 .keep_app-portage_layman-0 -rw-r--r-- 1 root root 57 Jun 11 07:23 make.conf -rw-r--r-- 1 root root480 Jun 11 07:23 overlays.xml So I *should* be safe to accept the changes that dispatch-conf suggests, right? Now there's another confusion. This just got committed to the efl overlay: http://cia.vc/stats/project/e/.message/1897db5 Note that the dev says we should be moving back to the enlightenment overlay :-) With all these changes it's hard to give firm advice, except to say this: If conf-update wants to make changes to package categories, and eix on your machine gives the same new ones as the new config file, then make the change. Otherwise find out why you are out of step. having said that, yes it does look like you have enlightenment overlay uninstalled and the efl one installed. And it looks like you are now going to switch them back around again. Life on the bleeding edge is fun, right? -- alan dot mckinnon at gmail dot com
