REPLY: 2:230/0 665b86cc
MSGID: 2:292/2226 6697e244
CHRS: CP850 2
TZUTC: 0200

   Hello Benny!

01 Jun 24 20:31, you wrote to Maurice Kinal:


 BP> so i need to spend time on make git ebuilds so it still keep stable, i
 BP> wish if husky would change to one single tarball with would make
 BP> sources lot more stable with single path and builds on every install,
 BP> have multi tarballs makes it possible to have 2 tarball sources not
 BP> compatible with api functions with can break updates

 BP> also lost the binkp source, hope i could make a none root build test
 BP> to see if it atleast compile without errors, if it do then i know what
 BP> ebuilds to create

I've noticed there's a significant amount of cleanup and documentation work
needed within the Husky project, but I don't mean to cast blame on anyone.

I've just started writing a somewhat detailed how-to guide for setting up an
FTN node on Debian and by using the github repositories for both binkd and
Husly. My goal is to share it and hopefully attract some geeks to
retrocomputing, the world of BBS and FTN networks. I also aim to possibly
bring back some former BBS operators who might think this technology is dead
and buried, which is not the case.

If you're interested, let me know via netmail and I'd be happy to share my
notes with you. Your assistance would be invaluable in identifying any
omissions or errors, helping to ensure the document is as clear as possible.

Any help is welcome.

Chris


--- GoldED+/LNX 1.1.5--b20170303
 * Origin:  ----> SPARK BBS  (2:292/2226)
SEEN-BY: 18/200 90/1 105/81 106/201 128/260 129/305 153/7715 218/700
SEEN-BY: 221/1 226/30 227/114 229/110 111 112 113 206 300 317 400
SEEN-BY: 229/426 428 470 550 616 664 700 266/512 280/464 282/1038
SEEN-BY: 291/111 292/789 854 2226 8125 301/1 320/219 322/757 335/364
SEEN-BY: 342/200 396/45 410/9 460/58 633/280 712/848 5075/35
PATH: 292/2226 789 854 229/426