It would appear that on Feb 28, Alan McKinnon did say:
>
> On Saturday 28 February 2009 09:54:00 Joe(theWordy)Philbrook wrote:
> > emerge --newuse enlightenment
> >
> > Before I install anything else???
>
> That will work fine the first time, as enlightenment has all the EFL libs as
> dependencies, and they in turn have their own dependencies, so they will all
> be pulled in correctly, including eina, eet, evas, etc
Great!
> I used to have a convoluted script thingy that listed every e17 app and lib
> and emerged them all. Now with portage sets I just stick everything in the
> set
> and 'emerge @e17'. It also keep my world file uncluttered.
I'm guessing '@e17' identifies the "set" that portage 2.2 or higher is to use.
> > 1) he says to: "emerge e"... But on my laptop where I've added the
> > overlay (but emerged no part of e yet) I just did an "emerge --ask e"
> > to see what it offered. "no ebuilds" As far as I can see the only E it
> > wants to give me is x11-wm/enlightenment 0.16.8.15 (says I've got
> > 0.16.8.11 Which must be e16... is 0.16.8.15 correct for E17??? And if
> > I do the emerge on that laptop won't I lose e16?? (I like to switch
> > off...) On my desktop I've enough hard drive space to run two copies
> > of Sabayon if need be to have both e16 and e17 available...
>
> Ah. That's because vapier changed the name of the ebuild from 'e' to
> 'enlightenment'. They should also be slotted so e16 and e17 do not clobber
> each other when portage figures out what to build.
>
> version 0.16.8.15 is the current release of e16
I was hoping that was a typo... I just mounted the partition where the
test installation of Sabayon I've been trying to "emerge" e17 on is
located. On which I thought I'd succeeded in emerging e17. But since I
was concerned about the keywords and hadn't added any components, I
hadn't built it an .xinitrc nor ran startx to test that theory...
UnderTree =-> pwd
/-sabaNext-sda11/usr/bin
UnderTree =-> ls e1*
e16
UnderTree =-> ls en*
enc2xs enchant-lsmod encode_keychange enum_chmLib env
enchant encodedv enscript enumdir_chmLib envsubst
UnderTree =->
So since e16 doesn't install from the dvd, I'm thinking THAT is what I
actualy emerged. (sigh)
> You might find versions 0.16.9999 in various places, that will probably be
> e17
> which is of course an entirely different thing altogether and merely shares a
> common name. You can easily run a recent e16 and e17 on the same machine
> (just
> like gnome and kde can co-exist) becuase all the files have different names
Since I'd have to reboot to see this on that /dev/sda11 Sabayon
install where I've been mucking with such things... It was easier to
forward this output to myself from the laptop where I'm a few steps
behind the test install. Since the laptop only has room for ONE fully
personalized Sabayon installation I don't do it there till I tried it on
the test install without borking it.
localhost layman # layman -S
* Running command "/usr/bin/svn up "/usr/local/portage/layman/sabayon""...
At revision 2791.
* Running command "/usr/bin/svn up "/usr/local/portage/layman/enlightenment""...
At revision 270.
*
* Success:
* ------
*
* Successfully synchronized overlay "sabayon".
* Successfully synchronized overlay "enlightenment".
localhost layman # emerge --search enlightenment
Searching...
[ Results for search key : enlightenment ]
[ Applications found : 1 ]
* x11-wm/enlightenment
Latest version available: 0.16.8.15
Latest version installed: 0.16.8.11
Size of files: 1,815 kB
Homepage: http://www.enlightenment.org/
Description: Enlightenment Window Manager
License: BSD
localhost layman # emerge --search e17
Searching...
[ Results for search key : e17 ]
[ Applications found : 0 ]
localhost layman #
I think that confirms two things.
1) The enlightenment overlay IS in place...
2) emerge still isn't offering me e17 ???
> You could always grab a recent portage ebuild, copy it to your local overlay
> and emerge it. It's been completely reliable for me, the last time portage
> broke something on any of my machine was in 2005 :-)
Perhaps that would solve the problems. I don't usually go outside of
whatever package versions my distro maintainers see fit to put in the
repositories. (adding the enlightenment overlay was new ground for me.)
Though I did add repos to OpenSuSE and Kubuntu to get E17. Still
emerge is a powerful tool. And this is the first thing I've wanted bad
enough to risk mucking with it for. (And at that on a test installation.)
You say 'grab', I'm thinking 'wget'? (from where?)
> Let me know if you haven't read up yet on local overlays and need some
> pointers.
Please! Any pointers you care to share will be MOST welcome.
(Along with any recommended reading. Though I must say most of the
official documentation I've found ever since I starting using linux has
usually sailed over my head. (I usually learn more from a few lines of
example than from several books of explanation.) Which is why I'm
frequently frustrated by man pages that seem more focused on
reminding some professor which features are in place rather than
telling the uninitiated (or forgetful) how to actually use the durned
command.
Your explanations on the other hand. Have so far made so much sense
to me that I'm starting to wish *_you_* had written all those man pages.
(I'd likely get more out of them.) This makes me wonder if perhaps you
are some kind of professional educator??
--
| ~^~ ~^~
| <*> <*> Joe (theWordy) Philbrook
| ^ J(tWdy)P
| \___/ <<[email protected]>>
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
