Re: Remove world editor in 2.1.0?
by Sydney Dykstra
Greetings!
It seems that no one has weighed their opinion in on this yet, so I shall share mine.
As much as I would like to see the level editor in the game for release 2.1.0, as it is a rather usefull
tool and is fun to play with, I do believe you are correct in thinking that it would be wise to remove it for this release.
As has been shown just by the lack of people responding to this email, we don't have too many people
with alot of time on their hands at the moment to help fix stuff, so the next best option is to simplify things instead.
Those are my thoughts.
Thanks!
-Sydney
_______________________________________________
tsc-devel mailing list -- tsc-devel(a)lists.secretchronicles.org
To unsubscribe send an email to tsc-devel-leave(a)lists.secretchronicles.org
2 years, 7 months
Build system for TSC3
by Marvin Gülker
Hi everyone,
since I have heard complaints about cmake every now and then, I'd
carefully ask if anyone wants to propose an alternative. Luiji earlier
suggested something custom written in Ruby. Since Ruby does with its
included Rake have a quite powerful task tool that can easily be
extended, that's one possibility I'd be willing to further explore (also
given that we have Ruby as a build dependency anyway due to mruby, which
does use Rake).
Note I'm only asking for suggestions so I can evaluate them. That
doesn't necessaryly mean that I'm going to switch the build system for
TSC3 anytime soon. I'm mostly fine with cmake except for a few quirks
and for me there's only little reason to switch.
Currently, TSC3 uses cmake just like TSC2. Since TSC3 will have a
noticably smaller number of dependencies (I hope), the cmake
configuration will be noticably easier as well.
I'd like to preclude autotools from possible build system
alternatives. I've struggled with it enough when I took over old SMC.
Marvin
--
Blog: https://mg.guelker.eu
PGP/GPG ID: F1D8799FBCC8BC4F
_______________________________________________
tsc-devel mailing list -- tsc-devel(a)lists.secretchronicles.org
To unsubscribe send an email to tsc-devel-leave(a)lists.secretchronicles.org
2 years, 7 months
Re: Server problems with systemd
by Ryan Gonzalez
Quick question for something I apparently missed:
On Thu, Jun 7, 2018 at 7:21 AM Marvin Gülker <m-guelker(a)phoenixmail.de>
wrote:
> it has long been known that our server has some problems, especially
> when starting up not all daemons are properly started. Most notably, the
> Cron daemon doesn't start.
>
So... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864720
Debian 9 should apparently work on kernel 2.6.32, but that kernel version
hasn't been supported by systemd since v34 from 2011 (!).
Now, on to the other stuff: is cron the only daemon that doesn't start?
Would you guys mind letting me take a look at the server and the systemd
setup? It just seems a bit odd that cron has trouble but *most* others
don't...
> Marvin
>
> --
> Blog: https://mg.guelker.eu
> PGP/GPG ID: F1D8799FBCC8BC4F
> _______________________________________________
> tsc-devel mailing list -- tsc-devel(a)lists.secretchronicles.org
> To unsubscribe send an email to tsc-devel-leave(a)lists.secretchronicles.org
>
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
_______________________________________________
tsc-devel mailing list -- tsc-devel(a)lists.secretchronicles.org
To unsubscribe send an email to tsc-devel-leave(a)lists.secretchronicles.org
2 years, 7 months
Re: Server problems with systemd
by Ryan Gonzalez
On June 7, 2018 7:21:00 AM Marvin Gülker <m-guelker(a)phoenixmail.de> wrote:
> Hi everyone,
>
> it has long been known that our server has some problems, especially
> when starting up not all daemons are properly started. Most notably, the
> Cron daemon doesn't start.
>
> It has been discovered that the reason is that our VPS is hosted on an
> OpenVZ system with kernel 2.6.32, which is too old for Debian Stretch's
> systemd. See https://github.com/systemd/systemd/issues/5236 (beware flamewar
That nosedived the second the guy brought in MariaDB...
>
> This is unfortunate and we'll have to think about how we continue. I
> have been in contact with our server sponsor (First Root) already, and
> they say that a kernel upgrade is outright impossible. Access to a KVM
> machine has been denied to us earlier, so that's not an alternative
> either. They have suggested we disable systemd and switch to SysV init
> for the time being.
>
> While this is certainly an option, it strikes me as problematic. Debian
> has ported much to systemd already and is not going to go back. I regard
> the alternative distribution Devuan as no professional alternative that
> could be used. We have different options now.
>
> 1. We could, for now, remove systemd and replace it with SysV init,
> hoping that First Root at some point upgrades their OpenVZ
> installation. This sounds easiest to me for the moment.
Question: how much is this Debian version dependent on sysvinit?
> 2. We could switch from Debian to a non-systemd distribution (hard to
> find a professional one, believe me).
There's always CentOS 6, which uses that old kernel version but still gets
security updates until 2020.
> 3. We could host our infrastructure elsewhere.
>
> Option 3 means leaving our sponsor or paying for a KVM machine. xet7 has
> offered to host our infrastructure on his employer's cloud machine, but
> as they're US-based this might be giving us trouble under the GDPR which
> I as the project lead do have to take into consideration as I'm a EU
> citizen.
If the company offers service to EU customers, shouldn't they already be
GDPR-compliant?
>
> Option 3 also is going to cause a lot of work as everything needs to be
> ported. I don't think I have enough free time for this available at the
> moment.
>
> Any thoughts on different alternatives are highly appreciated. I even
> thought I could set aside a Raspberry Pi at my home and have it run
> everything, but it turns out that hosting servers at my home violates my
> ISP's terms of service, so this option is out as well. Sending email
> from customer IPs also doesn't do any good, they're always
> hard-blacklisted as spam sources.
I'd offer my VPS, but it's dirt cheap ($10/year) and randomly goes
down...not really ideal...
In theory, depending on how much we directly use systemd, could we switch
the main distro (e.g. to CentOS 6) but then throw up a Debian container
inside it? That way the config could be nearly identical, but the part
touching the kernel would be compatible.
>
> Marvin
>
> --
> Blog: https://mg.guelker.eu
> PGP/GPG ID: F1D8799FBCC8BC4F
> _______________________________________________
> tsc-devel mailing list -- tsc-devel(a)lists.secretchronicles.org
> To unsubscribe send an email to tsc-devel-leave(a)lists.secretchronicles.org
_______________________________________________
tsc-devel mailing list -- tsc-devel(a)lists.secretchronicles.org
To unsubscribe send an email to tsc-devel-leave(a)lists.secretchronicles.org
2 years, 7 months
