On 22/04/18 14:26, Carsten Haitzler (The Rasterman) wrote:
[...]
Everything is working fine.
then explain the meson error you pasted.
I already have, about three times. It was because I typed the wrong
package name.
id meson install? can you install it?
Yes, once I retyped the apt command it insatlled perfectly.
it still doesn't change the fact that you have a meson package that is
uninstallable
No, it's installed.
for some reason related to the repo dataset you have.
No, nothing to do with it.
some of your dataset is broken. you can continue to pretend it's not even
though you pasted the error yourself. i'm repeating myself.
I think we'd better stop this; I'm wasting your time.
then explain the error you yourself pasted. install meson. does it install?
I have explained this already several times. Possibly not clearly.
explain why dpkg itself says there are held packages? is it wrong?
It was only wrong for that command. I think it may be a very trivial bug
in apt or dpkg.
and that package is broken. it is not needed to run enlightenment, but if you
ever need to compile it it will be needed.
We shall see. I wanted to do this just to see if meson worked (given
that I had terrible problems with it a few years ago on another project).
I had good success with compiling eft/enlightenment/terminology in a
previous version that compiled perfectly on several platforms a couple
of years ago; that used normal ./configure;make;make install so I am
interested to see if meson offers anything better.
at no point am i saying that it is needed now for enlightenment to run.
No, that was never a question.
i'm trying to help you by pointing out you have problems with your system there
and this may lead to more issues in future. you seem to not want that help,
even though your yourself saw the exact error and pasted it and now deny that
any issues exist, so i may as well give up.
I appreciate your concern and help. I just think you have misunderstood
the position, possibly through my poor explanations. I'm happy to be
proved wrong, though.
then THAT is the problem. meson depends on a non-existent package.
IFF that is the problem, then it's a problem for the Mint packagers. I'm
not seriously concerned because I'm only doing this out of interest,
having had problems with meson some years ago.
i installed ubuntu in a vm a few weeks back to test efl stuff there and i
installed meson and ninja-build because ninja-build *IS* ninja. the ninja pkg
name was already taken in ubuntu at least for some other software that is not
the ninja make/build tool.
Aha. NOW some new information. I was unaware of that. Perhaps the Mint
packagers mistook one for the other. Strange that there is no report of
it, especially as Mint uses meson for their own builds, apparently.
so i know at least on ubuntu ninja-build is the
correct package dependency for meson. i am not sure about mint, but considering
the closeness of their heritage i think that my assumption here would be right.
Yes, that makes perfect sense. I did not have this extra information.
and that is the ONLY thing i am talking about here. your meson package install
failure. everything else you mention is not relevant.
I never raised anything except the meson/ninja problem. I think some
others did contribute other information though.
Let's leave it rest until I am ready to experiment.
///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
