On 21/04/18 06:37, Carsten Haitzler (The Rasterman) wrote:
you didn't even have to install meson if it's already compiled
binaries. meson is needed to compile terminology and enlightenment
Right. I was installing meson because the web site said so.
But it turned out (thanks to your help) that I don't need to compile
terminology and enlightenment because I was able to back-track over the
dud-package problem.
on the cmdline or not should make no difference. a package (meson)
needs to be installed. ninja-build is a dependency of meson
Right. But the web site said just "ninja" so I typed ninja. Not ninja-build.
and it cannot install that/ something is seriously wrong with the
package repository/ies you are using
No. I obviously haven't explained this clearly enough:
1. I read web site at https://www.enlightenment.org/docs/distros/start
2. It says I need basic tools: git. autoconf (2.59 or better), automake
(1.10 or better), autopoint, libtool, gettext, meson and ninja
3. I type (as in email of 18/04/18 20:58)
apt install git autoconf automake autopoint libtool gettext meson ninja
4. apt says The following packages have unmet dependencies: meson :
Depends: ninja-build (>= 1.6) but it is not going to be installed
5. Massimo said "there is no package named ninja, you should
remove it from the apt command line."
6. I type
apt install git autoconf automake autopoint libtool gettext meson
7. Works perfectly. It installs ninja-build as a dependency of meson.
Nothing is broken in any repo; just the instructions refer to ninja
instead of ninja-build (and it's not needed explicitly anyway because it
gets included as a dependency of meson).
in that it is broken with a package (meson) that is uninstallable
because a dependency of it is unable to be installed (doesn't exist
or is too old a version as it wanted >= 1.6). your problem lies in
your repositories and those packages.
No. I don't understand why you think the repo is broken. There is no
evidence for this.
But apt needs much better error reporting, because it fails to identify
WHY the package could not be installed, and because it used the name of
a package which was not requested (ninja-build instead of ninja). But
perhaps it doesn't have that information.
///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
