Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    PERL    |    Support for the Perl scripting language    |    79 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 16 of 79    |
|    Jame Clay to Benny Pedersen    |
|    FTN::Database/ftnpldb    |
|    21 Sep 11 11:22:38    |
      > 01 Oct 2010 17:58, Jame Clay wrote to All:       >> I will be using that Perl module (which is also hosted to CPAN)       >> for Nodelist processing, for loading the nodelists in to the SQLite       >> database for further processing there.              > tryed to use this today under gentoo, with the fidonet overlay made by me,       > everything works :)               Glad to hear it!                     > i just miss one single thing now, nodelistDir load into db              > ----- ftnpldb.cfg begins -----       > ....       > ----- ftnpldb.cfg ends -----               That looked fine...                     > eq load all files from nodelister not just nodelist               If they are same type of nodelist, the current code will try to load the       most recent. If there are different nodelists there, like Fidonet       (nodelist.???) and Linuxnet (linuxnet.???), then it needs to be called       separately for each type.                     > tryed "perl ftnpldb-nodelist -c ftnpldb.cfg -v load" with works ok, but only       > loads nodelist.day               What other nodelist files are actually present?                     > where do i extend this ?, calling ftnpldb-nodelist pr nodelist file ?               If they are different domains, then yes. I have 5 FTN nodelists for the 5       different domains I'm in. For something like FamilyNet, for instance, the       command line I use is like this:              ftnpldb-nodelist -c $CFGFILE -f fmlylist -d fmlynet -v load                       Now, if what you want to do is load multiple nodelists of the same type or       domain, that is not yet in the code but is where I'm doing with it. The way       it is now, only the (presumably) most recent nodelist for a particular domain       is kept in the database. Where I'm going with the code; that use case (only 1       nodelist of a particular domain in the database) will still be possible but it       will also be possible to load multiple nodelists of the same domain into the       database. So one could load a couple (or a set) of nodelists for the same       domain, perhaps for comparison purposes. (And/or for a web app where one       could look up info for any nodelist...)               I have started on that but the changes have not yet been pushed to the       public respositories and are certainly not far enough along to put on CPAN as       yet or to hatch out in the PERL File echo...                             Jame              --- BBBS/LiI v4.01 Flag        * Origin: Rocasa BBS (1:120/546)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca