Bug#478904: cron script for apt needs improvement

[Osamu Aoki <osamu@debian.org>]

Hi, thanks.

On Fri, May 02, 2008 at 12:20:12PM -0300, Otavio Salvador wrote:
> Osamu Aoki <osamu@debian.org> writes:
> I do like your proposal and would like to know if you'd like to start
> a bzr branch to work on that and then we can upload it to experimental
> until Lenny is released.

Thanks.   I will try.  Any site should I look besides archive site.

> I'd like to get testing on that before add it to sid and this would
> rock to stay at experimental for a while now.

Sure.

> Can you create a bzr branch and point it for merging for us?

I am cvs/svn/git user.  Give me some time to learn bzr.  I just made bzr
branch here.  (It was slow.)

The second code I posted is very usable.  I am only naturing commets etc.

2 questions:

Question 1:

Where should message go?  stdout or stderr? As I inhereted, there seems
to be no consistency.
 * debug message when turned on.
 * error message from commands
 * error mesage from script

Question 2:

Do you think current choice of apt-conf variables have to stay.  I do
not like 3 irregular variables.

APT::Archives::MaxAge
APT::Archives::MinAge
APT::Archives::MaxSize

Why not use APT::Periodic:: here.  (I am OK with Dir::*)

I am wondering what should I do:
 * Keep these variable names as they are. (current)
 * Switch variable names but support old ones for compatibility.
 * Switch variable names completely and do not support old ones.

I like last option but I can do any one of them to get accepted.

Osamu

PS: My wish are to use:

APT::Periodic::ArchiveMaxAge
APT::Periodic::ArchiveMinAge
APT::Periodic::ArchiveMaxSize
APT::Periodic::Debug    --- new one addded for debug echo