Olivier Mueller a écrit:

On Thu, 2004-04-08 at 22:54 -0700, Robin H. Johnson wrote:

...

find -type d | xargs chmod g+rwsx Somebody has been messing with the checked out contents of the htdocs, and made a serious permissions mess and lots of dupes (and broken my cronjob):

oops, that was me, sorry. I had a "cd /home/groups/p/ph/phpmyadmin/htdocs/phpMyAdmin ; cvs update -d ; head -20 ChangeLog ; chmod -R g+rwx /home/groups/p/ph/phpmyadmin/htdocs" in my .bash_history, and I suppose it's what created the problems.

...

My cronjob automatically updates the ./phpMyAdmin dir every 3 hours.

I guess it's the purpose of /home/groups/p/ph/phpmyadmin/htdocs/updatecvs.sh ? Nice work, is it running on your personal SF shell account crontab, or are there project-based crontabs too?

It is his personal crontab. I am running one also, for home page news refresh.

...

Then BOTH Oliver (swix) and Marc (lem9) need to do: cd /home/groups/p/ph/phpmyadmin/htdocs chgrp -R phpmyadmin . find -type d | xargs chmod g+s find | xargs chmod g+rw

(did that approx a week ago, hope it's fine now).

Suggestion: What about also generating the cvs version (http://www.phpmyadmin.net/cvs/) on a daily basis via cron?

regards, Olivier

We could but maybe it's better to generate it when we feel it's stable enough (not in the middle of a modification). Not sure about that tho. Marc

On Fri, 2004-04-16 at 10:09 +0200, Michal Čihař wrote:

On 15.04.2004 16:29 -0400, Marc Delisle wrote:

...

Olivier Mueller a écrit:

...

Suggestion: What about also generating the cvs version (http://www.phpmyadmin.net/cvs/) on a daily basis via cron?

We could but maybe it's better to generate it when we feel it's stable enough (not in the middle of a modification).

Not sure about that tho.

cvs snaspshots don't have to be stable, I'd vote for daily generating.

[+1] we can just generate them when we are all (europe/canada) sleeping (or supposed to :), so for example at 6 am GMT ? Olivier

On Fri, 2004-04-16 at 09:32 -0400, Marc Delisle wrote:

...

...

cvs snaspshots don't have to be stable, I'd vote for daily generating. [+1] we can just generate them when we are all (europe/canada) sleeping (or supposed to :), so for example at 6 am GMT ?

Ok I will do it.

maybe it's possible to add that feature directely to robbat's script... or just call the create-release script from cron, but there is the cvs login/pw question problem there (probably a small issue). Olivier

On Fri, 2004-04-16 at 09:54 -0400, Marc Delisle wrote:

Olivier Mueller a écrit:

...

On Fri, 2004-04-16 at 09:32 -0400, Marc Delisle wrote:

...

...

...

cvs snaspshots don't have to be stable, I'd vote for daily generating.

[+1] we can just generate them when we are all (europe/canada) sleeping (or supposed to :), so for example at 6 am GMT ?

Ok I will do it.

maybe it's possible to add that feature directely to robbat's script... or just call the create-release script from cron, but there is the cvs login/pw question problem there (probably a small issue).

Olivier

I think the best is to call create-release.sh, but I wonder which first parameter we should pass it. Second parameter is HEAD by default.

Should we do create-release.sh snapshot ? Which could produce filenames like phpMyAdmin-YYYYMMDDHHMM.xxxx

would be the easiest, aber would require a "fix" to make it work via cron (now it requires a manual "[enter]" for the cvs login) and it asks a question (which could be optional if the script is run with the option "snapshot", ok...). I'd suggest to keep the .cvsignore and CVS dirs in cvs release, to allow testers use 'cvs update' too... : so this line should be ignored in 'snapshot mode' : "find phpMyAdmin \( -name .cvsignore -o -name CVS \) -print0 | xargs -0 rm -rf"

Another question: do we need to keep the tree generated by this script? I find it confusing in http://www.phpmyadmin.net/cvs to see a phpMyAdmin-2.6.0-dev subdir.

afaik it's there for 'historical reason' :-) so could be removed after generation of the archives, no problem. Olivier