On Sat, 16 Dec 2017 22:50:36 +0000 Peter Flynn <pe...@silmaril.ie> said:
> [Sorry, I should have made this a new thread long ago.] > > On 29/11/17 00:27, Carsten Haitzler wrote: > > On Tue, 28 Nov 2017 20:49:55 +0000 Peter Flynn <pe...@silmaril.ie> said: > > > >> On 28/11/17 00:05, Carsten Haitzler wrote: > >>> On Mon, 27 Nov 2017 20:38:30 +0000 Peter Flynn <pe...@silmaril.ie> > said: > >> [snip] > >>>> Does anyone have suggestions. I can't find a page describing > >>>> how to replace Moksha with E22. >>> > >>> looks like it needs a newer efl install. apt-get -f install ? or > >>> remove efl, enlightenment and anything that depends on these from > >>> bodhi and maybe compile your own? >> > >> Should I do all this from a Ctl-Alt-F1 console, rather than from > >> the X session (which would be Moksha) where you presumably can't > >> remove a package while it's in use (or can you?) > > > you can. linux != windows. you are allowed to pull the rug from > > under yourself (delete files that are in use). BUT this may have > > consequences. E will survive a short while like this until it needs > > data from data files (e.g. theme) and when it needs new data and > > checks... it won't find the files there and things will begin to go > > south. So you have a window of opportunity. remove, replace (fast) > > then restart e (ctl+alt+end keybinding for fastest way)... > After some experimentation I pulled out of this path entirely. > > I successfully compiled EFL from source (with autoconf and make...more > on this below) but the fact that Bodhi runs its own version of the EFL > libs makes replacement a much more difficult task. Not because of the > problems you mention above, but because getting rid of its own EFL libs > (and eventually Moksha and its own Terminology) means there are a couple > of dozen dependencies that it drags down with it. > > > fyi i am replacing all of my efl and e install all the time (many > > times a day) > > Yes, but not on Bodhi :-) > > > as i suggested. remove efl entirely and everything that depends on > > it... > > In practice this simply won't work on Bodhi...it may be theoretically > possible, but the tangle of dependencies goes too deep. > > > then start again with something newer. you could self-compile > > efl+e+terminology+... > I trashed the whole sorry mess and went to look again at Mint, which at > least doesn't come with E by default (in fact, doesn't appear to have E > in its repos at all :-) so it's a good candidate for installation. > > I had tried it before (Maté) but while it installed, it refused to > reboot because it had messed up the Grub installation. However, in the > meantime it appears that the Cinnamon release of Mint 18.3 now tolerates > the deficiencies of the XPS 15 to the extent that it actually installed > *and* rebooted! (I blogged this for anyone who wants the details at > http://blogs.silmaril.ie/peter) > > This now means all I have to do is get E running. I appear to have three > options (please correct me if I am wrong). Working on the basis that > Mint is Ubuntu-based, > https://www.enlightenment.org/docs/distros/ubuntu-start says: > > 1. PPA (niko2040); I haven't tried this yet so I don't know if it works > for Mint. It failed on Bodhi but that was because of library > dependency conflicts. > > 2. Build from source using Meson; never used Meson, and it won't > install: > > Command "python setup.py egg_info" failed with error code 1 in > /tmp/pip-build-ruyohi9b/meson/ > You are using pip version 8.1.1, however version 9.0.1 is available. > You should consider upgrading via the 'pip install --upgrade pip' > command. > > This is nearly as bad as ant, another much-vaunted replacement for > make which causes more trouble than it is worth. just use the meson PACKAGES. apt-get install meson ninja :) > 3. (preferred) configure;make;make install (except it's autoconf rather > than make, which is OK). > > So get EFL from Github, run ./autoconf.sh in efl, and make. This > actually *worked* (amazingly) on Bodhi, but now fails on Mint 18.3: > see next message. > > There also seems to be a fundamental problem with the downloaded code from: > > git clone https://git.enlightenment.org/core/enlightenment.git > git clone https://git.enlightenment.org/apps/terminology.git > git clone https://git.enlightenment.org/apps/rage.git > > None of them have any autoconf.sh so it's impossible to build them. well rage and terminology have autogen.sh .. autoGEN.sh. there never was an autoconf.sh. always autogen.sh. these 3 all moved to meson. read README and INSTALL files... they tell you what to do with meson. > ///Peter > > On 28/11/17 00:40, Dave wrote: > >>> What happened when you ran "apt-get -f install"? > > To answer the question, it went around in circles, saying it was going > to install the missing dependency and then saying it couldn't do so > because there was an issue with dependencies. But I'm done with Bodhi. > +++ > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
