🚀 go-pugleaf

In article <520@ssbell.UUCP> kent@ssbell.UUCP (Kent Landfield) writes:
>In article <1123@ssp15.idca.tds.philips.nl> jos@idca.tds.PHILIPS.nl (Jos Vos) writes:

>A patch is in testing right now to be released next week that has an
>additional method of archiving. ....
> ....
>example:
>	volume89/Jul/890706.01 or volume89/890706.01

I already looked in the code and saw that it would be quite easy
to add an archive method that popen's a user program (specified in some
way) that puts a plain filename on stdout.
Than I can play with SysV date +%... as much as I like.
The next step could be to let that program generating a relative
pathname, in that case the program could be just a script with
	date '+volume%y/%h/%y%m%d'
Only the problem with the .seq suffix should be solved then,
if you *want* to solve it.

>The test as to whether an article is already archived is done by checking 
>if the archive file exists. I'm not sure what you mean by BIG. ...

I only meant that the previous item (generating own filenames) would
cause that you can't detect an article --- filename-for-saving relation
anymore. Doesn't that problem also occur in your proposed scheme?
What about the .archived file mentioned somewhere in the documentation?

>>-  How are crosspostings handled?
>Currently, crosspostings are *not* handled. ...

It becomes a problem if you want to use rkive for archiving a lot of
newsgroups, i.e. not only sources. But I can imagine it's quite
difficult to handle that correctly (w.r.t. the rkive.cf file's lists).

>>-  Is it not possible to use rkive as a program directly
>>   from the sys file (that is, with the article as stdin)?
>No. rkive is meant to run from cron and not receive the articles from stdin.

Still a nice item for the IDEAS file :-)

-- 
-- ######   Jos Vos   ######   Internet   jos@idca.tds.philips.nl   ######
-- ######             ######   UUCP         ...!mcvax!philapd!jos   ######