On 22/04/18 06:12, Carsten Haitzler (The Rasterman) wrote:
[...]
our job is to provide the source code that gets compiled, so out
instructions will be for that. :) the general instructions on our
download page where the downloads are source at any rate. :)
Yep. I used to rely on it in the days when I recompiled from scratch for
each platform I used.
But since Niko's .debs worked so well, I've been using them — until the
trouble with the most recent ones. But since you gave me the fix to
backtrack, I no longer need to compile anything, so I was just trying to
see if meson was as broken as it was when I last looked at it.
that doesn't matter. meson required ninja-build. you installed some
unrelated ninja package that is going to consume some space but
otherwise have no effect.
But nothing was installed the first time: the original command failed
for the reason given. Apt was doing its job correctly, just
badly-worded. The second time it worked perfectly.
the problem is meson + its dependencies in the package repos you use.
that may mean mint is totally broken. it may mean repos you have
added are broken as a result you end up with this. either way you
have a broken package repo situation when it comes to meson.
No, absolutely not. I cannot understand why you still think this.
Everything is working fine.
as above. ... the meson package in the distribution you use and/or its
dependencies when taken as a whole in your distribution or your use of it
including added or changed repository url's is broken.
No, it's fine. I simply typed an additional unnecessary package and apt
correctly refused to install it.
yes they are. you posted the error yourself:
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.
That was a result of my typing an additional unnecessary package name
the first time. The error message is bogus. Nothing was installed,
nothing was held. Apt merely thought there was because the command failed.
that is an error for you. perhaps you have held back certain packages from
updating that cause ninja-build not to update to a newer version etc. (as i
said before that perhaps it's there but unable to install a new enough version).
No, there are no hold-backs, previous versions, or anything of the sort.
yes there is. see above. you yourself provided it. "unmet dependencies".
No, that was just the result of my typing an additional unnecessary
package name.
ninja-build WAS REQUESTED.
Yes, wrongly. I should not have typed that name.
it was REQUESTED by the meson package.
No, *I* requested it...wrongly.
I don't know what
you've done, but a little bit of investigating like installing ninja-build
But there is no package ninja-build in this distro. Just a package
ninja. I am assuming this package contained the functionality of
ninja-build, whatever that may be, because the ninja package satisfied
the requirements of meson.
i'm trying to let you know you have a problem
I appreciate that but I don't think that is the case.
In any event it's moot. I am happy with the backtracking I did to
recover terminology, so I have no desire to recompile anything.
I *will* need meson for a completely unrelated project I am
experimenting with, but that's a different question.
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
