@Dennis Emojicode 0.5 is out!

@Phlarx That works. Thanks!

@Phlarx Done.

@WheatWizard tio.run/…

@betseg And with a little luck, it will be just as painful to compile as 0.4. >_>

it was hard? huh. it took me about a minute to download and compile everything.

Might be confusing it with Emoji.

One of them was a royal pain.

@MartinEnder B&C does too. Enabled options for all three.

@betseg Yes, it was Emojicode. We actually had to freeze it to a certain commits because later ones refused to compile.

we? :O

Yes, @AndrewSavinykh is the main contributor to github.com/TryItOnline/tiosetup, which automates the installation and updates of TIO's languages.

10026  git clone github.com/emojicode/emojicode .
10027  mkdir build
10028  cd build
10029  cmake .. -GNinja
10030  sudo pacman -S ninja
10031  cmake .. -GNinja
10032  sudo pacman -S allegro
10033  cmake .. -GNinja
10034  ninja
10035  ninja dist
10036  ./emojicodec

and its installed

Aside from the fact that I don't have pacman, that cmake overflows the heap on my server, and that it will install packages where I don't want them.

But don't worry, we'll get it installed one way or another.

it installed in /usr/local/bin/emojicode in my pc

Yes, TIO has its interpreters in /opt.

it's the first writable part in $PATH btw

if you put /opt/ in $PATH before the other dirs?

@Dennis I've always wondered, why /opt, of all places?

man hier:

> /opt This directory should contain add-on packages that contain static files.

/opt is a place where you have free reign over the directory structure and don't have to afhere to the FHS. Most languages on TIO don't.

Having your interpreters in /usr/local/bin will only serve to cause trouble if there are two with the same name.

What's the fhs?

@betseg That varies wildly by distro. Also, I don't want most of this stuff in the path as is.

@Phoenix en.m.wikipedia.org/wiki/Filesystem_Hierarchy_Standard

$ temp = $PATH
$ PATH = /opt/emojicode/whatever:$PATH
$ ninja dist
$ PATH = $temp

ninja?

ninja-build.org

some build system

@betseg And it's on TIO now.

300 MB in dependencies. sighs

@Dennis thanks :)

@Dennis wow

@Dennis Can you please pull Brachylog?

@Fatalize Pulled and currently syncing.

@Dennis synwhat?

you mean the cache or something?

Syncing. All installations/updates/whatever are done on the main server where they can't break languages, then the arena servers are synced with the main one.

so the arena servers have their own copies of a language?

The arena servers are indentical to the main one, with the exception of logs and running systemd services.

If the main server goes down, an arena server can assume the role of the main server by executing a couple of commands.

@Dennis Thanks!

So aside from making housekeeping easier, it also provides redundancy.

so you don't have to pull, pull, pull and pull right?

That's one reason, yes. For compiled interpreters, I actually had to take one arenas out of rotating, pull, compile, test, put it back in rotation, and repeat the process for the remaining arenas servers.

Now I just pull, compile, test, and sync. Much simpler.

heh

Also the first step towards semi-automatic updates.

@Dennis Nice updates to Tio

The biggest advantage is that I do not have to rollback any changes that cause problems. The affected language is simply blacklisted and not synced until the problem is resolved.

@Dennis Could you pull cQuents?

@Dennis could you pull Cubically?