TZUTC: -0400   
   MSGID: 56575.sync_sys@1:103/705 2b83fa52   
   REPLY: 56574.sync_sys@1:103/705 2b83dd65   
   PID: Synchronet 3.20a-Linux master/7b14d9036 Oct 26 202 GCC 14.2.1   
   TID: SBBSecho 3.20-Linux master/6c4d4a187 Oct 25 2024 21:11 GCC 12.2.0   
   COLS: 80   
   BBSID: KK4QBN   
   CHRS: CP437 2   
   NOTE: SlyEdit 1.89c (2024-10-19) (ICE style)   
     Re: Build error after pull   
     By: nelgin to kk4qbn on Sat Oct 26 2024 23:58:15   
      
    ne> I am not a big fan of how Synchronet works with git but I have created my   
    ne> own update scripts to mitigate some of the main issues that it was causing   
    ne> me without having to do this git stash crap every time I did changes and   
    ne> whatnot. It's not perfect but it suits my needs. Git itself does provide   
    ne> some useful tools for the developers and I like their bug reporting and   
    ne> it's easy to view the code history.   
      
   For my use it really doesnt present any issues really less for me to have to   
   do than what i did with CVS, once the initial pull is done, I do mine kinda a   
   little different though because I keep my working bbs file tree and the source   
   tree seperate, eg   
      
   Working:   
      
   /sbbs/exec   
   /sbbs/ctrl   
   /sbbs/xtrn   
   ...   
      
   Source Tree:   
      
   /sbbs/repo/src   
   /sbbs/repo/ctrl   
   /sbbs/repo/xtrn   
   ...   
      
   I have too many of the JS files modified and don't want to accidently screw   
   anything up so just copy JS files that have changed/new etc.. manually I'm   
   sure there are much easier ways to do it, but this is the way I do it. works   
   for me :) and theres really not much I have to put into it.   
      
      
    ne> 3.20 has come a long way to help sysops get up and running quickly from   
    ne> when I and a lot of other sysops started. There was no binkit integration,   
    ne> tickit lacked some features, there was no automatic setting up of fido and   
    ne> FTN networks with the init script or installation of doors and dosemu was   
    ne> hit and miss. That said, there is still quite a learning curve and it's   
    ne> not just plug and play, you have to understand all the terminology that   
    ne> goes with it, and can be daunting task for many new sysops.   
      
    ne> That said, again, there have been a bunch of new boards popup since I   
    ne> started so there's people still out there interested in grinding at it. I   
    ne> don't want it to sound like people have it easier these days...which I   
    ne> guess they do in a way, no need to find separate mailers and tossers and   
    ne> get them working with the bbs, but the need for knowledge is still there   
    ne> because you need to know how they work together and interact with the   
    ne> bbs...sorry, I'm rambling...   
      
   I've always thought for the most part that putting a BBS up should'nt be too    
   "Plug N' Play" or easy. There should be a degree of difficulty there that the   
   sysop should go through. I might be alone in that thought, But I really   
   would'nt want to see what a bbs scene would look like if ANYONE could install   
   the software and have it runing very quickly and easily.. we still enjoy a   
   certain degree of, well I wouldnt say privacy, but were able to set ourselves   
   apart a bit from the intenet and social media as a whole.   
      
   Rambling can be good.   
   ---   
   Tim (kk4qbn)   
   +o kk4qbn.synchro.net   
    þ Synchronet þ KK4QBN BBS - kk4qbn.synchro.net - Chatsworth, GA USA   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/187 153/757 7715   
   SEEN-BY: 154/10 30 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426