• htick

    From Martin Foster@2:250/1.333 to All on Mon Aug 2 11:22:14 2021
    Hello All!

    I'm in need of a tic file processor for Linux and was wondering if it's possible to compile 'htick' without the rest of the husky stuff.

    If that's not possible, what else would I need to build 'htick'.

    Regards,
    Martin

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Bitz-Box - Bradford - UK (2:250/1.333)
  • From Michael Dukelsky@2:5020/1042 to Martin Foster on Mon Aug 2 13:41:38 2021
    Hello Martin,

    Monday August 02 2021, Martin Foster wrote to All:

    I'm in need of a tic file processor for Linux and was wondering if
    it's possible to compile 'htick' without the rest of the husky stuff.

    If that's not possible, what else would I need to build 'htick'.

    You have to build Husky libraries before building htick. So first you have to grab the sources.

    mkdir ~/husky
    cd husky
    git clone https://github.com/huskyproject/huskylib.git
    git clone https://github.com/huskyproject/smapi.git
    git clone https://github.com/huskyproject/fidoconf.git
    git clone https://github.com/huskyproject/areafix.git
    git clone https://github.com/huskyproject/htick.git

    Now you take the makefile configuration common for the subprojects:
    wget https://raw.githubusercontent.com/huskyproject/huskybse/master/huskymak.cfg
    and update it according to your needs. It should be in the same 'husky' directory. After that you may build and install htick.

    cd huskylib
    make && sudo make install
    cd ../smapi
    make && sudo make install
    cd ../fidoconf
    make && sudo make install
    cd ../areafix
    make && sudo make install
    cd ../htick
    make && sudo make install

    You have htick now. If you used static linking (DYNLIBS=0 in huskymak.cfg), you may delete the static libraries libhusky.a, libsmapi.a, libfidoconfig.a, libareafix.a from LIBDIR you configured in huskymak.cfg. It is not necessary to store them after you have built htick.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Martin Foster@2:250/1.333 to Michael Dukelsky on Thu Aug 5 09:33:40 2021
    Hello Michael!

    *** Monday August 02 2021 13:41, you wrote to me:

    I'm in need of a tic file processor for Linux and was wondering
    if it's possible to compile 'htick' without the rest of the husky
    stuff.

    If that's not possible, what else would I need to build 'htick'.

    You have to build Husky libraries before building htick. So first you
    have to grab the sources.

    mkdir ~/husky
    cd husky
    git clone https://github.com/huskyproject/huskylib.git
    git clone https://github.com/huskyproject/smapi.git
    git clone https://github.com/huskyproject/fidoconf.git
    git clone https://github.com/huskyproject/areafix.git
    git clone https://github.com/huskyproject/htick.git

    Now you take the makefile configuration common for the subprojects:
    wget https://raw.githubusercontent.com/huskyproject/huskybse/master/hu skymak.cfg and update it according to your needs. It should be in the
    same 'husky' directory. After that you may build and install htick.

    cd huskylib
    make && sudo make install
    cd ../smapi
    make && sudo make install
    cd ../fidoconf
    make && sudo make install
    cd ../areafix
    make && sudo make install
    cd ../htick
    make && sudo make install

    You have htick now. If you used static linking (DYNLIBS=0 in huskymak.cfg), you may delete the static libraries libhusky.a,
    libsmapi.a, libfidoconfig.a, libareafix.a from LIBDIR you configured
    in huskymak.cfg. It is not necessary to store them after you have
    built htick.

    Everything worked just fine apart from 'config' wasn't installed in the location that I'd defined in 'huskymak.cfg'. In fact, I don't think it got installed at all, so I just manually copied it to my desired location.

    Thank you very much indeed for the clear and concise step by step instructions, very much appreciated.

    Regards,
    Martin

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Bitz-Box - Bradford - UK (2:250/1.333)
  • From Wilfred van Velzen@2:280/464 to Martin Foster on Thu Aug 5 12:12:35 2021
    Hi Martin,

    On 2021-08-05 09:33:40, you wrote to Michael Dukelsky:

    You have to build Husky libraries before building htick. So first you
    have to grab the sources.

    mkdir ~/husky
    cd husky
    git clone https://github.com/huskyproject/huskylib.git
    git clone https://github.com/huskyproject/smapi.git
    git clone https://github.com/huskyproject/fidoconf.git
    git clone https://github.com/huskyproject/areafix.git
    git clone https://github.com/huskyproject/htick.git

    Now you take the makefile configuration common for the subprojects:
    wget https://raw.githubusercontent.com/huskyproject/huskybse/master/hu
    skymak.cfg and update it according to your needs. It should be in the
    same 'husky' directory. After that you may build and install htick.

    cd huskylib
    make && sudo make install
    cd ../smapi
    make && sudo make install
    cd ../fidoconf
    make && sudo make install
    cd ../areafix
    make && sudo make install
    cd ../htick
    make && sudo make install

    You have htick now. If you used static linking (DYNLIBS=0 in
    huskymak.cfg), you may delete the static libraries libhusky.a,
    libsmapi.a, libfidoconfig.a, libareafix.a from LIBDIR you configured
    in huskymak.cfg. It is not necessary to store them after you have
    built htick.

    Everything worked just fine apart from 'config' wasn't installed in the location that I'd defined in 'huskymak.cfg'. In fact, I don't think it got installed at all, so I just manually copied it to my desired location.

    Thank you very much indeed for the clear and concise step by step instructions, very much appreciated.

    Indeed!

    It should be in the faq, or documented somewhere. I also always struggle to get the modules compiled in the right order, and with the right options, when I move my fido setup to a new system every couple of years...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Kai Richter@2:240/77 to Wilfred van Velzen on Thu Aug 5 19:32:10 2021
    Hello Wilfred!

    05 Aug 21, Wilfred van Velzen wrote to Martin Foster:

    Thank you very much indeed for the clear and concise step by step
    instructions, very much appreciated.

    Indeed!

    It should be in the faq, or documented somewhere.

    Well, in a far far away past, there was something like RTFM. Let me point to the trees in the forest today.

    (And forgive me for posting links, the files should be included in the distribution archives too.)

    ###
    https://github.com/huskyproject/htick/blob/master/INSTALL.md

    Instruction to build htick

    Please read the files (especially README.Makefiles) in the husky-common (huskybse) package FIRST!
    ###

    I think this first step reminder is placed into any module.


    ###
    https://github.com/huskyproject/huskybse/blob/master/INSTALL

    Contents
    ========

    I. Overview

    II. Compiling the Source Code

    III. How to Configure and Use the Software


    I. Overview
    ===========

    The Husky Fidonet software package is split into different "modules". A
    module is a library or a program. In order to compile any Husky program, you will at least have to download the following modules:

    huskybse Husky Base, contains *instructions*, a template compilation
    configuration file, and sample configs.
    huskylib Common declarations and functions for Husky programs
    smapi The Squish Message API library.
    fidoconf The Fidoconfig library.

    In addition, you need the programs that you want to use, like "hpt" (the tosser), "htick" (the ticker), "msged" (the mail editor), and others.

    ###

    The concept is well described from my point of view.

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Michael Dukelsky@2:5020/1042 to Martin Foster on Thu Aug 5 22:18:00 2021
    Hello Martin,

    Thursday August 05 2021, Martin Foster wrote to Michael Dukelsky:

    Everything worked just fine apart from 'config' wasn't installed in
    the location that I'd defined in 'huskymak.cfg'.

    'config' is not installed automatically, its location in huskymak.cfg lets the Husky programs know where to find it.

    Thank you very much indeed for the clear and concise step by step instructions, very much appreciated.

    You are welcome.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Michael Dukelsky@2:5020/1042 to Wilfred van Velzen on Thu Aug 5 22:22:08 2021
    Hello Wilfred,

    Thursday August 05 2021, Wilfred van Velzen wrote to Martin Foster:

    Thank you very much indeed for the clear and concise step by step
    instructions, very much appreciated.

    Indeed!

    It should be in the faq, or documented somewhere. I also always
    struggle to get the modules compiled in the right order, and with the right options, when I move my fido setup to a new system every couple
    of years...

    I began updating makefiles and the documentation on installing software and understood that the makefiles are so bad that it is better to rewrite them from scratch. The work turned out to be quite large, so please wait until I finish the makefiles and documentation.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Moscow, Russia (2:5020/1042)
  • From Wilfred van Velzen@2:280/464 to Kai Richter on Thu Aug 5 22:01:15 2021
    Hi Kai,

    On 2021-08-05 19:32:10, you wrote to me:

    It should be in the faq, or documented somewhere.

    Well, in a far far away past, there was something like RTFM. Let me point to the trees in the forest today.

    [...]

    The concept is well described from my point of view.

    Well I managed to compile htick in december last year. But I needed some help with conflicting and not all that clear information in the documentation of the different modules. (You even commented in the thread)

    So I wouldn't call it "well described".

    Ideally you should only have to type 'make' once in the htick directory, which would automatically make the different husky libraries in the right order and with the right options, that htick depends on, if they are not yet build and installed...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Michael Dukelsky on Thu Aug 5 22:07:31 2021
    Hi Michael,

    On 2021-08-05 22:22:08, you wrote to me:

    It should be in the faq, or documented somewhere. I also always
    struggle to get the modules compiled in the right order, and with the
    right options, when I move my fido setup to a new system every couple
    of years...

    I began updating makefiles and the documentation on installing software and
    understood that the makefiles are so bad that it is better to rewrite them from scratch. The work turned out to be quite large, so please wait until I
    finish the makefiles and documentation.

    That will be great! Thanks!

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Kai Richter@2:240/77 to Wilfred van Velzen on Fri Aug 6 21:38:20 2021
    Hello Wilfred!

    05 Aug 21, Wilfred van Velzen wrote to Kai Richter:

    It should be in the faq, or documented somewhere.

    Well, in a far far away past, there was something like RTFM.

    The concept is well described from my point of view.

    Well I managed to compile htick in december last year. But I needed
    some help with conflicting and not all that clear information in the documentation of the different modules. (You even commented in the
    thread)

    So I wouldn't call it "well described".

    True. I didn't understand that you are now much deeper into details of different modules. My point of view was on the basic sequence of the building process.

    Ideally you should only have to type 'make' once in the htick
    directory, which would automatically make the different husky
    libraries in the right order and with the right options, that htick depends on, if they are not yet build and installed...

    Ideally i wouldn't have to use 'make' at all. 'apt/rpm/pkg/yours install htick' should do the trick. ;) Maybe i'm too much used to husky but i don't see htick as a standalone programm. It's a part of a toolset and the base tool is huskybase. Once the huskymak.cfg of the huskybse is set up any other module should compile on the fly. The december issue was a bug. A global parameter for all husky modules in the huskymak.cfg was overrided. If a module doesn't follow the huskymak.cfg settings then it's worth a bug report.

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Wilfred van Velzen@2:280/464 to Kai Richter on Sat Aug 7 12:08:26 2021
    Hi Kai,

    On 2021-08-06 21:38:20, you wrote to me:

    The concept is well described from my point of view.

    Well I managed to compile htick in december last year. But I needed
    some help with conflicting and not all that clear information in the
    documentation of the different modules. (You even commented in the
    thread)

    So I wouldn't call it "well described".

    True. I didn't understand that you are now much deeper into details of different modules.

    I am?

    My point of view was on the basic sequence of the building process.

    And that process isn't very well documented in my opinion.

    Ideally you should only have to type 'make' once in the htick
    directory, which would automatically make the different husky
    libraries in the right order and with the right options, that htick
    depends on, if they are not yet build and installed...

    Ideally i wouldn't have to use 'make' at all. 'apt/rpm/pkg/yours install htick' should do the trick. ;)

    Wouldn't that be nice! ;)

    But you would have to convince a lot of distribution maintainers to support husky, just for maybe a few hundred (at best) users... Ain't gona happen.

    Maybe i'm too much used to husky but i don't see htick as a standalone programm.

    It is for me.

    It's a part of a toolset and the base tool is huskybase. Once the huskymak.cfg of the huskybse is set up any other module should compile
    on the fly.

    Is that documented? ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Oli@2:280/464.47 to Wilfred van Velzen on Sat Aug 7 12:28:44 2021
    Wilfred wrote (2021-08-07):

    Ideally i wouldn't have to use 'make' at all. 'apt/rpm/pkg/yours
    install htick' should do the trick. ;)

    Wouldn't that be nice! ;)

    The build process is just the test for the newcomer. If they fail at the first stage, the husky config is to complicated for them anyway ;P.

    But you would have to convince a lot of distribution maintainers to support husky, just for maybe a few hundred (at best) users... Ain't gona happen.

    Not more than a dozen per package format. My guess is the only actively used packaged fidonet software is binkd.

    ---
    * Origin: . (2:280/464.47)
  • From Jeff Squires@1:120/457 to Oli on Sun Aug 8 08:09:18 2021
    The build process is just the test for the newcomer. If they fail at the first stage, the husky config is to complicated for them anyway ;P.

    So your saying that it only for the "elite". Sounds like a excuse for a poorly documented and hard to install software...
    --- Mystic BBS v1.12 A47 2021/06/19 (Windows/32)
    * Origin: commconnbbs.net (1:120/457)
  • From Kai Richter@2:240/77 to Wilfred van Velzen on Sun Aug 8 22:15:34 2021
    Hello Wilfred!

    07 Aug 21, Wilfred van Velzen wrote to Kai Richter:

    The concept is well described from my point of view.

    So I wouldn't call it "well described".

    True. I didn't understand that you are now much deeper into
    details of different modules.

    I am?

    Yes, you are. :) For me the list of commands (that you liked) in this echo did match to the sequence explanation of the huskybse INSTALL file.

    My point of view was on the basic sequence of the building
    process.

    And that process isn't very well documented in my opinion.

    Please compare the list of commands in this thread to the examples of the INSTALL file. I can't see much difference. The sudo command is missing there.

    Ideally you should only have to type 'make' once in the htick

    Ideally i wouldn't have to use 'make' at all. 'apt/rpm/pkg/yours
    install htick' should do the trick. ;)

    Wouldn't that be nice! ;)

    To tell my real opinion, no, it would not be nice if fidonet node software would be a one-click installation. This would result in high administration workload in the *C structure and some weeks later into dead node listings or nodelist clearings. Fast install and fast forgotten.

    But you would have to convince a lot of distribution maintainers to support husky,

    Sorry, again no. You could set up and maintain your own repository. The user have to add the repo url into the apt settings.

    just for maybe a few hundred (at best) users...

    Cancel "few". 21 hpt "star" markers, 10 network members. I don't know if there is way to see a husky download counter.

    Maybe i'm too much used to husky but i don't see htick as a
    standalone programm.

    It is for me.

    What about the dual configuration in your non-husky installation and the fidoconfig required for htick? How do you keep them in sync?

    It's a part of a toolset and the base tool is huskybase. Once the
    huskymak.cfg of the huskybse is set up any other module should
    compile on the fly.

    Is that documented? ;-)

    Yes, in the husky base document. That is the inital primer, read first.

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Kai Richter@2:240/77 to Oli on Sun Aug 8 22:35:10 2021
    Hello Oli!

    07 Aug 21, Oli wrote to Wilfred van Velzen:

    The build process is just the test for the newcomer. If they fail at
    the first stage, the husky config is to complicated for them anyway
    ;P.

    Sounds mean but i think that matches reality exactly.

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Wilfred van Velzen@2:280/464 to Kai Richter on Mon Aug 9 21:38:44 2021
    Hi Kai,

    On 2021-08-08 22:15:34, you wrote to me:

    The concept is well described from my point of view.

    So I wouldn't call it "well described".

    True. I didn't understand that you are now much deeper into
    details of different modules.

    I am?

    Yes, you are. :) For me the list of commands (that you liked) in this echo did match to the sequence explanation of the huskybse INSTALL file.

    First you have to know you have to start with huskybse. That isn't even mentioned in the htick/INSTALL file.

    My point of view was on the basic sequence of the building
    process.

    And that process isn't very well documented in my opinion.

    Please compare the list of commands in this thread to the examples of the INSTALL file. I can't see much difference. The sudo command is missing there.

    See above.

    To tell my real opinion, no, it would not be nice if fidonet node
    software would be a one-click installation. This would result in high administration workload in the *C structure and some weeks later into
    dead node listings or nodelist clearings. Fast install and fast
    forgotten.

    This is already a problem! :-(

    But you would have to convince a lot of distribution maintainers to
    support husky,

    Sorry, again no. You could set up and maintain your own repository. The user have to add the repo url into the apt settings.

    Correct.

    Maybe i'm too much used to husky but i don't see htick as a
    standalone programm.

    It is for me.

    What about the dual configuration in your non-husky installation and the fidoconfig required for htick? How do you keep them in sync?

    It hasn't been a problem sofar... The binkd config is also separate, makenl is separate.


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Kai Richter@2:240/77 to Wilfred van Velzen on Mon Aug 9 23:49:14 2021
    Hello Wilfred!

    09 Aug 21, Wilfred van Velzen wrote to Kai Richter:

    I am?

    Yes, you are. :) For me the list of commands (that you liked) in
    this echo did match to the sequence explanation of the huskybse
    INSTALL file.

    First you have to know you have to start with huskybse. That isn't
    even mentioned in the htick/INSTALL file.

    I'm sorry, but it is. And i posted it already. With a pointer to the source. ###
    https://github.com/huskyproject/htick/blob/master/INSTALL.md

    Instruction to build htick

    Please read the files (especially README.Makefiles) in the husky-common (huskybse) package FIRST!
    ###

    Please compare the list of commands in this thread to the
    examples of the INSTALL file. I can't see much difference. The
    sudo command is missing there.

    See above.

    I did a copy/paste. Nothing was invented. You could confirm my assertion by checking it for yourself.

    Fast install and fast forgotten.

    This is already a problem! :-(

    We don't see many new installs in R24.

    What about the dual configuration in your non-husky installation
    and the fidoconfig required for htick? How do you keep them in
    sync?

    It hasn't been a problem sofar... The binkd config is also separate, makenl is separate.

    I know but my question was "how"? Do you add a new link in the non-husky tosser/areafix and do the same for the fidoconfig htick again?

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Wilfred van Velzen@2:280/464 to Kai Richter on Tue Aug 10 21:51:07 2021
    Hi Kai,

    On 2021-08-09 23:49:14, you wrote to me:

    Fast install and fast forgotten.

    This is already a problem! :-(

    We don't see many new installs in R24.

    There are other Regions/Nets, where you see regular new systems. They install mostly Mystic, apply for a node number, mostly for nostalgic reasons, and after a while they disappear without a trace, because the current fidonet doesn't conform to their memories of the old days. But their nodelist entries remain forever...

    What about the dual configuration in your non-husky installation
    and the fidoconfig required for htick? How do you keep them in
    sync?

    It hasn't been a problem sofar... The binkd config is also separate,
    makenl is separate.

    I know but my question was "how"? Do you add a new link in the non-husky tosser/areafix and do the same for the fidoconfig htick again?

    Yes, there is no other way. But you only do this maybe a couple of times a year at most, so it doesn't bother me...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Kai Richter@2:240/77 to Wilfred van Velzen on Tue Aug 10 23:45:34 2021
    Hello Wilfred!

    10 Aug 21, Wilfred van Velzen wrote to Kai Richter:

    Do you add a new link in the non-husky tosser/areafix and do the
    same for the fidoconfig htick again?

    Yes, there is no other way. But you only do this maybe a couple of
    times a year at most, so it doesn't bother me...

    Well, i think i'm far too lazy for that. ;)

    If you install htick as a module into an existing husky environment very much of the config is already done.

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)