Module submission - pcb-cvs

[Zbigniew Luszpinski]

Monday 04 of June 2007 22:17:07 Duncan Gibson wrote:
> > but which other way is around to keep cvs-modules up to date?
>
> Surely if there is a particular cvs-module that you want to keep
> as up-to-date as possible you can copy it to your zlocal and set
> the UPDATED field to give you the rebuild schedule that you want.
> Then you get updates when you want them without forcing everyone
> else to rebuild more often than they need.
>
> That's the power of Lunar: you can tweak the modules as you need
> as long as you do it in your own zlocal.

There is no need to use zlocal. Just lin it whenever you want. This task can 
be automated using cron or started during boot.

Looking so far the most reasonable idea comes from Auke.
However I will be opting for giving random update day by module maintainer 
instead of 1st day of every month because of:
1) maintenance reason: it is easier to handle single update faults in a month  
instead of plenty of them on one day. The automatic cvs-like updates may fail 
sometimes because there is no human control during packaging,
2) I'm a fan of international wires offload by splitting traffic when possible 
and mirroring, you know keep the net clean and so on...
3) single updates can be easily reported and traced by users. The report: "It 
broke today" and a huge list of updated modules looks as a nightmare to me.

Saying about random date I'm thinking about Auke's UPDATED=`date -u +%Y%m01` 
where 01 is replaced with different number 01...28 (no more because of 
February) per 'live' module.

Zbigniew