 |
Forums |
Admin  Start New Thread
By: Doga Armangil
 RE: "-f N" option [ reply ]
2007-07-23 01:06
|
Users who need this "catch-up" functionality can use the --horizon option (introduced in version 3.0.0), which provides similar functionality.
|
By: Doga Armangil
RE: "-f N" option [ reply ]
2007-01-03 18:37
|
Hi Mike,
You are right, such a catch-up feature would be useful for new users. I will probably implement it in the next version.
Thanks for the comment.
|
By: Mike Felix
RE: "-f N" option [ reply ]
2007-01-02 23:16
|
Would it be possible to add a catch-up mode to be run once that would simply add all content in a feed to the history without downloading them? It would make converting to your podcatcher easier for people with existing lists of feeds.
I like your podcatcher far more than any other solution I've found, but the way I listen to podcasts requires back_catalog; therefore in order to begin using it I modified your code a bit to provide this one-time capability because I didn't want to download tons of MBs of shows I'd already heard.
|
By: Nobody
RE: "-f N" option [ reply ]
2006-01-16 17:41
|
I have found a workaround for my problem:
First of all i have downloaded N enclosures from N feeds with the "one" strategy. Then I have determined all enclosures with the aid of the verbose option. Put them (s/^Enclosure: //) into the cache file. Then I can switch to the "back_catalog" stategy.
Regards
Heiko
|
By: Nobody
RE: "-f N" option [ reply ]
2006-01-15 09:43
|
Hello Doga,
it's ok that you don't plan an alternative way of doing this -- I have no authorisation to demand such features. But I wanted to discuss them in this forum...
What I still want to say is that the "one" strategy is not exactly what I want, because when there are no new enclosures available, the podcatcher gets the next *older* enclosure/s. I only want to download the newest N enclosures (if required). The "new" strategy is not practical, because there might be 2+ enclosures available between the last podcatcher run and now.
The size option doesn't help also, since it limits the size of the whole cache directory. Since the implementation of the subfolder per feed-option it would be practical to be able to restrict the size for certain feed-directories.
Best regards,
Heiko
|
By: Doga Armangil
RE: "-f N" option [ reply ]
2006-01-14 15:56
|
Hello,
The "one" strategy does exactly want you want, please see below. You can use this in cronjobs. I do not plan to add an alternative way of doing this, at least in the immediate future. Sorry.
Thanks for your comments.
|
By: Nobody
RE: "-f N" option [ reply ]
2006-01-14 14:01
|
Hello Doga,
thank you for your hints.
But wouldn't it be a nice feature to provide an option in order to restrict the maximum nunber of enclosures to be downloaded?
Then one would be able to call podcatcher in a cronjob (in combination with the back_catalog strategy) downloading the last N enclosures without thinking about cache sizes.
Best regards,
Heiko
|
By: Nobody
RE: "-f N" option [ reply ]
2006-01-13 08:50
|
Hello Doga,
I see. Thank you for your explanation.
I wanted to restrict the maximum numnber of enclosures to be downloaded. I wish to combine such a restriction with the back_catalog strategy. With such a feature I would be able to use the back_catalog strategy without the need to download the entire enclosure list.
Is this possible?
Best regards,
Heiko
|
|
|
