Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-18 Thread Peter Flynn 

On 18/12/17 19:12, Stephen Houston wrote:

The wireless gadget shows connection strength. The netstatus gadget will
show traffic. Wireless gadget is available at
enlightenment/gadgets/wireless.git and the netstatus gadget comes with E.


Connman is always going to be a replacement for nm, right? Given that 
every distro I have seen comes with nm by default, and that users are 
already going to be connected before they go to install E.


I'm just a little wary of connman breaking nm permanently, giving me no 
path back if connman turns out not to be usable.


I don't see netstatus anywhere — does it also work with nm?

P

--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-18 Thread Stephen Houston 
The wireless gadget shows connection strength. The netstatus gadget will
show traffic. Wireless gadget is available at
enlightenment/gadgets/wireless.git and the netstatus gadget comes with E.

On Mon, Dec 18, 2017, 1:09 PM Peter Flynn  wrote:

> On 18/12/17 15:30, Stephen Houston wrote:
> > The wireless gadget also supports network manager, at a basic level, now.
>
> It certainly does, or I wouldn't be writing this :-)
>
> I was just curious to know if connman offered anything more, like an
> indicator showing traffic or connection strength.
>
> ///Peter
>
>
> --
> 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
>
--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-18 Thread Peter Flynn 

On 18/12/17 15:30, Stephen Houston wrote:

The wireless gadget also supports network manager, at a basic level, now.


It certainly does, or I wouldn't be writing this :-)

I was just curious to know if connman offered anything more, like an 
indicator showing traffic or connection strength.


///Peter

--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-18 Thread Stephen Houston 
The wireless gadget also supports network manager, at a basic level, now.

On Mon, Dec 18, 2017, 4:52 AM Carsten Haitzler  wrote:

> On Sun, 17 Dec 2017 20:37:38 + Peter Flynn  said:
>
> > On 17/12/17 14:47, Carsten Haitzler wrote:
> > > On Sun, 17 Dec 2017 12:56:18 + Peter Flynn 
> said:
> > [...]
> > >> If I try to add ninja-build to the install command, it says
> > >>
> > >>  The following packages have unmet dependencies:
> > >>   ninja-build : Conflicts: ninja but 0.1.3-2 is to be installed
> > >>  E: Unable to correct problems, you have held broken packages.
> > >
> > > well obviously ... you have a conflict.
> >
> > Even I can see that. But I don't know how to solve it.
> >
> > > remove ninja then and install ninja-build...
> >
> > Removing ninja was what caused the problem in the first place.
> >
> > > correct. it's no longer make. it's meson + ninja.
> >
> > OK, thanks.
> >
> > > yes. only meson. i think you have issues at your end. see above. just
> fix
> > > your conflicts.
> >
> > I'm afraid I have work to do, so it'll have to stay broken for the
> > moment. My only issue is with software that doesn't install, as I
> reported:
> >
> >  >> Command "python setup.py egg_info" failed with error code 1 in
> >  >> /tmp/pip-build-ruyohi9b/meson/
> >
> > a lot of projects have moved to meson:
> > >
> > > gtk+
> > > glib
> > > mesa
> > > wayland
> > > weston
> >
> > I'm an end user of Linux, not a Linux developer. They must use whatever
> > toolset is appropriate; those aren't projects I would ever need to
> > compile myself.
> >
> > Problem fixed, however; after testing in a sacrificial Mint environment,
> > the PPA solution worked just fine.
>
> I'm unsure of all the details of your pain, but it seems you have a trail
> of
> pain and TBH It's a rare day i go distro hoping just to have things work
> for
> me. I've really used/installed 5 distros over the past 20+ years of Linux
> (Slackware, then RH, then Debian, Ubuntu and for the past 3 years or so
> Arch). I
> use Arch these days and it works for me. Sure. I've had to fiddle on some
> UEFI-only systems to make it boot right, and some "rootfs is on nvram":
>
> /dev/nvme0n1p1 on / type ext4 (rw,noatime,discard,commit=1800,data=ordered)
>
> like stuff. But it just involves some learning, fiddling and making things
> work. No it's not "just click next and it just boots" but it seems you're
> having even more pain later on which is even more work compared to just
> fixing the core issue: why things don't boot. Perhaps just investigating
> this
> and figuring it out might be worth it for you. You'll get past it into
> pastures
> of "less pain" and learn something.
>
> > One curiosity: E suggests I install connman for my network connections.
> > Last time I looked at connman it was still being developed. Is it worth
> > switching from whatever regular distros provide (nm, I assume)?
>
> I have only used connman for many many many years. works for me.
>
> > ///Peter
> >
> >
> >
> --
> > 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
>
--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-18 Thread Carsten Haitzler 
On Sun, 17 Dec 2017 20:37:38 + Peter Flynn  said:

> On 17/12/17 14:47, Carsten Haitzler wrote:
> > On Sun, 17 Dec 2017 12:56:18 + Peter Flynn  said:
> [...]
> >> If I try to add ninja-build to the install command, it says
> >>
> >>  The following packages have unmet dependencies:
> >>   ninja-build : Conflicts: ninja but 0.1.3-2 is to be installed
> >>  E: Unable to correct problems, you have held broken packages.
> > 
> > well obviously ... you have a conflict.
> 
> Even I can see that. But I don't know how to solve it.
> 
> > remove ninja then and install ninja-build...
> 
> Removing ninja was what caused the problem in the first place.
> 
> > correct. it's no longer make. it's meson + ninja.
> 
> OK, thanks.
> 
> > yes. only meson. i think you have issues at your end. see above. just fix
> > your conflicts. 
> 
> I'm afraid I have work to do, so it'll have to stay broken for the 
> moment. My only issue is with software that doesn't install, as I reported:
> 
>  >> Command "python setup.py egg_info" failed with error code 1 in
>  >> /tmp/pip-build-ruyohi9b/meson/
> 
> a lot of projects have moved to meson:
> > 
> > gtk+
> > glib
> > mesa
> > wayland
> > weston
> 
> I'm an end user of Linux, not a Linux developer. They must use whatever 
> toolset is appropriate; those aren't projects I would ever need to 
> compile myself.
> 
> Problem fixed, however; after testing in a sacrificial Mint environment, 
> the PPA solution worked just fine.

I'm unsure of all the details of your pain, but it seems you have a trail of
pain and TBH It's a rare day i go distro hoping just to have things work for
me. I've really used/installed 5 distros over the past 20+ years of Linux
(Slackware, then RH, then Debian, Ubuntu and for the past 3 years or so Arch). I
use Arch these days and it works for me. Sure. I've had to fiddle on some
UEFI-only systems to make it boot right, and some "rootfs is on nvram":

/dev/nvme0n1p1 on / type ext4 (rw,noatime,discard,commit=1800,data=ordered)

like stuff. But it just involves some learning, fiddling and making things
work. No it's not "just click next and it just boots" but it seems you're
having even more pain later on which is even more work compared to just
fixing the core issue: why things don't boot. Perhaps just investigating this
and figuring it out might be worth it for you. You'll get past it into pastures
of "less pain" and learn something.

> One curiosity: E suggests I install connman for my network connections. 
> Last time I looked at connman it was still being developed. Is it worth 
> switching from whatever regular distros provide (nm, I assume)?

I have only used connman for many many many years. works for me.

> ///Peter
> 
> 
> --
> 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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-17 Thread Peter Flynn 

On 17/12/17 14:47, Carsten Haitzler wrote:

On Sun, 17 Dec 2017 12:56:18 + Peter Flynn  said:

[...]

If I try to add ninja-build to the install command, it says

 The following packages have unmet dependencies:
  ninja-build : Conflicts: ninja but 0.1.3-2 is to be installed
 E: Unable to correct problems, you have held broken packages.


well obviously ... you have a conflict.


Even I can see that. But I don't know how to solve it.


remove ninja then and install ninja-build...


Removing ninja was what caused the problem in the first place.


correct. it's no longer make. it's meson + ninja.


OK, thanks.


yes. only meson. i think you have issues at your end. see above. just fix your
conflicts. 


I'm afraid I have work to do, so it'll have to stay broken for the 
moment. My only issue is with software that doesn't install, as I reported:


>> Command "python setup.py egg_info" failed with error code 1 in
>> /tmp/pip-build-ruyohi9b/meson/

a lot of projects have moved to meson:


gtk+
glib
mesa
wayland
weston


I'm an end user of Linux, not a Linux developer. They must use whatever 
toolset is appropriate; those aren't projects I would ever need to 
compile myself.


Problem fixed, however; after testing in a sacrificial Mint environment, 
the PPA solution worked just fine.


One curiosity: E suggests I install connman for my network connections. 
Last time I looked at connman it was still being developed. Is it worth 
switching from whatever regular distros provide (nm, I assume)?


///Peter


--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-17 Thread Peter Flynn 

On 17/12/17 14:10, Philippe Jean Guillaumie wrote:
[...]

Yes, this is the right way to get the latest meson version in Ubuntu.
Works flawlessly in 16.04 LTS and 17.10.


Alas not in Mint, apparently.


To remove locally installed meson use:
pip3 uninstall meson first (you don't need sudo).

Then you'll be able to uninstall python3-pip and ninja-build if you want.


Moot now.


Read the docs (Ubuntu-start) and check out my script (batden's
script=oneartful.sh): you will find answers to all your questions.


I looked at the script and it looks very useful if you're running 
Ubuntu. I wasn't prepared to risk the fragility of the newly-installed 
system by editing the system name to allow sylvia.



Bodhi is a really good distro, but Bodhi != Ubuntu and Moshka != E23.


I wasn't expecting it to be Ubuntu, but I *was* expecting it to run E. 
I'm curious to know what they hoped to gain by forking it that way.


///Peter


--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-17 Thread Carsten Haitzler 
On Sun, 17 Dec 2017 12:56:18 + Peter Flynn  said:

> On 17/12/17 00:56, Carsten Haitzler wrote:
> > On Sat, 16 Dec 2017 22:50:36 + Peter Flynn  said:
> [...]
> >> 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.
> > 
> > just use the meson PACKAGES.
> > 
> >apt-get install meson ninja
> 
> Because https://www.enlightenment.org/docs/distros/ubuntu-start said to 
> use sudo apt-get install ninja-build python3-pip
> 
> I did sudo apt-get purge ninja-build python3-pip to get rid of the two 
> packages I installed, but now if I try to apt-get install meson ninja I get
> 
> The following packages have unmet dependencies:
>  meson : Depends: ninja-build (>= 1.6) but it is not going to be
>  installed
> E: Unable to correct problems, you have held broken packages.
> 
> If I try to add ninja-build to the install command, it says
> 
> The following packages have unmet dependencies:
>  ninja-build : Conflicts: ninja but 0.1.3-2 is to be installed
> E: Unable to correct problems, you have held broken packages.

well obviously ... you have a conflict. remove ninja then and install
ninja-build...

> >> 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. 
> 
> My apologies...mistyping, I meant autogen.sh. Is it therefore impossible 
> to build enlightenment with autogen.sh and make?

correct. it's no longer make. it's meosn + ninja.

>  > read README and
>  > INSTALL files... they tell you what to do with meson.
> 
> Not useful if I can't get meson installed. Does this mean that support 
> for building will be only using meson in future? Is meson stable enough 
> for this move? It's clearly not there yet.

yes. only meson. i think you have issues at your end. see above. just fix your
conflicts. a lot of projects have moved to meson:

gtk+
glib
mesa
wayland
weston

... just to name a few.

> > But I'm done with Bodhi.
> >> +++
> 
> :-)  This is actually a pity, given their original philosophy.
> 
> ///Peter
> 
> 
> --
> 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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-17 Thread Philippe Jean Guillaumie 


Le 17/12/2017 à 13:56, Peter Flynn a écrit :
> On 17/12/17 00:56, Carsten Haitzler wrote:
>> On Sat, 16 Dec 2017 22:50:36 + Peter Flynn  said:
> [...]
>>> 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.

You can safely ignore the warning message about pip version (no upgrade
needed).

>> just use the meson PACKAGES.
>>
>>    apt-get install meson ninja
> 
> Because https://www.enlightenment.org/docs/distros/ubuntu-start said to
> use sudo apt-get install ninja-build python3-pip

Yes, this is the right way to get the latest meson version in Ubuntu.
Works flawlessly in 16.04 LTS and 17.10.

meson -v = 0.43.0

> I did sudo apt-get purge ninja-build python3-pip to get rid of the two
> packages I installed, but now if I try to apt-get install meson ninja I get

To remove locally installed meson use:
pip3 uninstall meson first (you don't need sudo).

Then you'll be able to uninstall python3-pip and ninja-build if you want.

> 
>    The following packages have unmet dependencies:
>     meson : Depends: ninja-build (>= 1.6) but it is not going to be
>     installed
>    E: Unable to correct problems, you have held broken packages.
> 
> If I try to add ninja-build to the install command, it says
> 
>    The following packages have unmet dependencies:
>     ninja-build : Conflicts: ninja but 0.1.3-2 is to be installed
>    E: Unable to correct problems, you have held broken packages.
>>> 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. 
> 
> My apologies...mistyping, I meant autogen.sh. Is it therefore impossible
> to build enlightenment with autogen.sh and make?
> 
>> read README and
>> INSTALL files... they tell you what to do with meson.

Read the docs (Ubuntu-start) and check out my script (batden's
script=oneartful.sh): you will find answers to all your questions.


> Not useful if I can't get meson installed. Does this mean that support
> for building will be only using meson in future? Is meson stable enough
> for this move? It's clearly not there yet.
> 
>> But I'm done with Bodhi.

Bodhi is a really good distro, but Bodhi != Ubuntu and Moshka != E23.

--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-17 Thread Peter Flynn 

On 17/12/17 00:56, Carsten Haitzler wrote:

On Sat, 16 Dec 2017 22:50:36 + Peter Flynn  said:

[...]

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.


just use the meson PACKAGES.

   apt-get install meson ninja


Because https://www.enlightenment.org/docs/distros/ubuntu-start said to 
use sudo apt-get install ninja-build python3-pip


I did sudo apt-get purge ninja-build python3-pip to get rid of the two 
packages I installed, but now if I try to apt-get install meson ninja I get


   The following packages have unmet dependencies:
meson : Depends: ninja-build (>= 1.6) but it is not going to be
installed
   E: Unable to correct problems, you have held broken packages.

If I try to add ninja-build to the install command, it says

   The following packages have unmet dependencies:
ninja-build : Conflicts: ninja but 0.1.3-2 is to be installed
   E: Unable to correct problems, you have held broken packages.

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. 


My apologies...mistyping, I meant autogen.sh. Is it therefore impossible 
to build enlightenment with autogen.sh and make?


> read README and
> INSTALL files... they tell you what to do with meson.

Not useful if I can't get meson installed. Does this mean that support 
for building will be only using meson in future? Is meson stable enough 
for this move? It's clearly not there yet.



But I'm done with Bodhi.

+++


:-)  This is actually a pity, given their original philosophy.

///Peter


--
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

Re: [e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-16 Thread Carsten Haitzler 
On Sat, 16 Dec 2017 22:50:36 + Peter Flynn  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 + Peter Flynn  said:
>  >
>  >> On 28/11/17 00:05, Carsten Haitzler wrote:
>  >>> On Mon, 27 Nov 2017 20:38:30 + Peter Flynn  
> 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

[e-users] E on Bodhi and Mint (was: Re: New applications -- menu/ibar entries

2017-12-16 Thread Peter Flynn 

[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 + Peter Flynn  said:
>
>> On 28/11/17 00:05, Carsten Haitzler wrote:
>>> On Mon, 27 Nov 2017 20:38:30 + Peter Flynn  
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.

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.

///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