Re: migrating slrn settings to tin

In Urs Janßen <urs@buil.tin.org> wrote:

[I don't know anything about slrn spool/slrnpull]
_if_ the slrn spool is in traditional spool format (I assume it is)
(and an active-file is provided (not required if using -n)) _reading_
should be no problem (but if it lacks NOV-files it may be slow(er); tin
could likely be used to create NOV-files if really needed).

Did a quick check:

~> slrnpull -d /tmp/slrnpull # ...
~> TIN_SPOOLDIR=/tmp/slrnpull/news \
TIN_ACTIVEFILE=/tmp/slrnpull/data/active tin # ...

Looks ok. For posting I used
inews_prog=/usr/local/bin/tinews.pl
in tinrc (tinews.pl comes with tin). Also ok.

With cache_overview_files tin created/used NOV-files in the default
location ${TIN_HOMEDIR:-"$HOME"}/.tin/.news-local which is ok for
single user access[1]. I doubt that it gives me a (big) win as long
as the number of articles per group is kept moderate (what moderate
is depends and disk/cpu/... speed; I guess all below around 10k should
not show a noticable difference, so you could skip overview creation
if you expire accordingly).

[1] for multi-user access you need to tweak settings, but I is
    slrnpull ment for multi-user access?

HTH,
urs