| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
there is no sense in me keeping it around when all it does is
add faff to writing the script
add useless noise to the filenames/paths
and enforces its opinions upon me which i dont agree with
and all for absolutely ZERO reason since i don't even have a feed in the
first place
if you want to take my scripts and package them into a dependencycontrol
feed, you are more than welcome to do so, provided you comply with the
terms of the licence. but your life is going to be a little bit harder
i'm afraid, sorry about that.
i will keep all the script_namespace, depctrl registration and such
around for the time being (removing it is >effort)
|
| |
|
|
|
|
|
|
| |
>write function specifically to help do a thing
>time passes
>have to do the thing again
>dont use function i wrote
genius
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
better than finding a file that's probably the config, parsing the json, and writing it back in,
for obvious reasons
turns out no i wasnt thinning out the soup too much
twas just right
Reason for adding values one by one in key-pair loop instead of just config = new_config:
> [01:31] arch1t3cht: oh, I think you can't assign entire tables to DependencyControl.config.c
> [01:31] arch1t3cht: like, you can't do DependencyControl.config.c = <my new config>,
> you should do DependencyControl.config.myfield = <my new value> and whatnot
> [01:32] arch1t3cht: because behind the scenes it uses metatable magic to track what field changes
> so it can merge its own changes with ones that other scripts made in the meantime
Co-Authored-By: arch1t3cht <arch1t3cht@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
no longer rewrites the entire config below the existing one(!)
added forgotten local variables, removed unnecessary ones
fixed a typo
|
| | |
|
| |
|
|
| |
oops
|
| |
|
