Relay Scripts Post-SVN

bumcheekcity

Active member
With the update to mafia now allowing SVNs, we can update all our relay scripts at once, and I think it'd be a great idea to have a single SVN holding updates to each relay script. Kind of like what I saw bUMRATS as being, but without it turning into one horrific and unmanageable file.

I'm happy to make a folder on my SVN for a community-relay override, and would add anyone who feels like they want to add things to it, unless anyone else has already done so. I thought initially that massive overrides (CHIT, BatMan), might be best in their own SVNs, but if anyone wants to chime in, feel free.

Worth it?
 

Bale

Minion
With the update to mafia now allowing SVNs, we can update all our relay scripts at once, and I think it'd be a great idea to have a single SVN holding updates to each relay script. Kind of like what I saw bUMRATS as being, but without it turning into one horrific and unmanageable file.


I think it is a bad idea. Sorry, but I will attempt to explain that claim.

First the problem: Let's say I like your topmenu.ash and many others in your svn archive, but prefer my own woods.ash and someone else's pyramid.ash. If all of those files are in your single svn /relay folder, then issuing the "svn update" command will update all of your relay script, potentially having difficulties merging with the completely unrelated relay scripts that I prefer to use.

Now the solution: The beauty of the "svn update" command is that if I have installed the 32 different relay scripts of Bumrats from 32 different SVNs, they are all checked for updates and potentially updated with a single use of that command. It doesn't matter if they are in one SVN archive or 32 different archives as far as the user is concerned. Sure, it will take a little bit longer to check 32 different SVNs, but if the mafia preference to check all scripts at logon is enabled, it will happen during breakfast along with the rest and the user will hardly notice. I will really prefer being able to pick and chose the overrides I want to use without getting stuck using overrides I do not favor.

tl;dr: Putting all 32 scripts in the same SVN /relay folder will remove choices from the user without much advantage to that user.
 
Last edited:

bumcheekcity

Active member
You make a fair point - I hadn't considered that. You'd recommend that rather than have:

Code:
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/ocean.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/topmenu.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/pandamonium.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/town_altar.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/campground.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/dungeon.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/shore.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/dungeons.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/ref
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/questlog.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/town_wrong.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/town_right.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/traveler.ash

We should have:

Code:
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS_ocean/relay/ocean.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS_topmenu/relay/topmenu.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS_town_altar/relay/town_altar.ash

etc.?
 

Bale

Minion
Small addendum: There is one instance I can think of where it would be a good thing to put a bunch of relay overrides into the same SVN folder. If the relays all work together like the wikilink overrides: desc_effect, desc_familiar, desc_item.php, desc_outfit and desc_skill by IceColdFever then they are obviously a group and should be listed that way.


You make a fair point - I hadn't considered that. You'd recommend that rather than have:

Code:
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/ocean.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/topmenu.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS/relay/town_altar.ash

We should have:

Code:
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS_ocean/relay/ocean.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS_topmenu/relay/topmenu.ash
A https://svn.code.sf.net/p/bumcheekascend/code/bUMRATS_town_altar/relay/town_altar.ash

etc.?

Yes!
 

roippi

Developer
Separating out elements that users may want to pick and choose into separate projects is generally good practice, yeah. You have to check out all of a project or none of it.

Once I implement dependencies, you can actually have an additional "package" project that itself contains no payload other than a list of other projects to checkout. In this way users who Want It All can install everything with one command rather than... well, more than one.
 
Top