How to install Livecode on the last Linux versions

[bogs]

Will try harder...

No worries, my posts aren't the easiest to follow to begin with

[mwieder]

Apparently the launch thing isn't important enough to fix (although it's interesting to note that apparently it did work in LC 7.0.6):
https://quality.livecode.com/show_bug.cgi?id=12876

[bogs]

Thank you for posting that link, I found it a fascinating read, and only 4 years old.

Maybe someone with access to the source could submit a pull and fix the spelling issue, before it becomes a teenager?

The command needed here is to run :> strace -fe trace=process /path/to/installer

It looks like the issue is as follows:
- The Community installer is trying to launch "LiveCode Community.x86_64", which doesn't exist (the binary is named "livecodecommunity.x86_64" for backwards-compatibility reasons)
- The Business installer is trying to launch "LiveCode Business.x86_64", which does exist

[FourthWorld]

Everyone has access to the source:
https://github.com/livecode/livecode

[bogs]

I wouldn't trust myself to just go muck around in that source for public consumption, at least not at my current levels, so let me rephrase what I said to be -

Maybe someone with access to the source who knows what they are doing could submit a pull and fix the spelling issue, before it becomes a teenager?

And despite what you said in another thread about companies, bugs, and software, while I agree that all software has bugs, maybe fixing known ones with in a year or two isn't such a bad goal.

[mwieder]

The installer isn't part of the FOSS code, so it's not on github. Peter B found the problem, but it's up to the team to fix it.

[FourthWorld]

The installer isn't part of the FOSS code...

That's weird. It's the least interesting part of the product from a technology standpoint. ::scratching head::

[mwieder]

That's weird.

Not really. The github repository allows you to build the community project. The installer has to handle all the different editions, check the licensing details, package all the myriad parts and unpack them into the appropriate places with proper permissions, etc. There are good reasons for keeping some proprietary parts private.

[FourthWorld]

Thanks. Yeah, I can understand that. I would have done it differently, but if I had a dollar for every time I've said that about their scripted components...

[bogs]

edit: also the "launch livecode" option at the end of the installation process doesn't work, but LC is installed and can be launched after that fails.

That has NEVER worked for me on any Linux installation in the last 13 years.

Try your distro x with the MATE desktop, I think you'll be surprised. The launch after install works on Linux Mint Debian Edition 2 (which uses the MATE desktop by default). Go figure, I think it must have been designed to work on Gnome2 and was just never updated.

[SparkOut]

Well maybe, but it has never launched on Windows after installation either.
It's not like it matters for that "one time only" so I don't suppose anybody's given it much attention.

[bogs]

Kind of curious if it launches on Mac after installation myself. but I can't test that one out with Lc9.x. Weird that it doesn't launch on Windows though. Did it ever launch on Windows after installing it?

[SparkOut]

Never that I know/can recall

[bogs]

Huh, just did a bug search on the db, no bug about it ever being reported (that I could find). Now I am REALLY curious if it works on Mac, any Mac users wanna fill us in

*Edit - I was mistaken (again), apparently our own Richard Gaskin filed a report about this here.

[bwmilby]

Mac is a drag and drop install from the disk image.