Closed rpdelaney closed 6 years ago
Branch. Some things to think about:
For my shitty attempt before I joined the team, see here.
I'd suggest a git repo within a git repo (!).
A submodule?
What language are you going to write the script in?
POSIX shell.
Yes.
@jbzdarkid added a build script in python. I have some reservations about having python2 dependencies in the build app, especially if we plan to use it for distribution eventually. Any objections to me rewriting it in POSIX?
What python2 deps does it have? I can upgrade to py3, if you need.
Sorry, I meant to say that I think we should avoid dependencies entirely: as nearly as possible, the build app should be self-contained and portable.
Python felt like the most portable way to distribute, since (iirc) bash isn't on windows and batch isn't on unix.
POSIX sh is everywhere: http://pubs.opengroup.org/onlinepubs/009695399/utilities/sh.html
6:00 PM - darkid »« \a\a\a Let's play!: so in a nutshell:
- Promod (official) should release a config.
- Promod should require that server owners that they use this config 2a. Server owners can modify the config slightly (readyup cosmetic changes, e.g.)
- (optional) Promod should release a plugin which verifies server owners are using this config. 6:01 PM - Kiss me ;) ♡ #March 1st: yea 6:01 PM - Kiss me ;) ♡ #March 1st: and jump rocks/bhop scripts should be nulled
(excerpt) Kissme getting frustrated at non-standard configs. This would be a good moment to standardize, or at least create a match config. I put it here because with a build script the above is very easy to enforce.
Since everybody runs linux now anyway, we could package a build script with promod.
:question: Should the build script include an spcomp binary, or attempt to download and compile it from source?
@jacob404 @jbzdarkid : Do you want this attached to a milestone or should I just work in a branch until it's ready to go?