On Sun, 17 Dec 2017 20:37:38 +0000 Peter Flynn <pe...@silmaril.ie> said:
> On 17/12/17 14:47, Carsten Haitzler wrote: > > On Sun, 17 Dec 2017 12:56:18 +0000 Peter Flynn <pe...@silmaril.ie> 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
