[Pkg-awstats-devel] Joining AWstats Team

[Sergey B Kirpichev]

On Tue, Jul 13, 2010 at 12:45 AM, Ken Neighbors <ken at nsds.com> wrote:
> Thanks, Sergey, for letting me know the missing piece to be able to submit
> changes to the git repository.

Please also request membership at the collab-maint team at
http://alioth.debian.org/projects/collab-maint/ (and add
as a note that you need it to work with us at the AWStats team)

> And also thanks for closing my bug reports.  I haven't had a chance to try
> out your fixes, but from your comments it looks goods.

I hope so.  Unfortunately, Jonas clearly lacks a time to review and
upload changes.

> In particular (bug #580699), I see your comment about taking my alternate
> suggestion of having update.sh and buildstatic.sh process the default
> awstats config file last so that it does not interrupt processing of any
> existing multi-site config files, and I agree that solution makes better
> sense to keep backwards-compatibility.  What did you mean by "This way the
> bug was fixed in CVS."?

Actually, this commit
http://git.debian.org/?p=collab-maint/awstats.git;a=commitdiff;h=702ac9f6c7e1399d6f1feaa4e7d1c442c60c1e2f;hp=5c7a5202b74dc88616ad42dfec4776bbee5454b3

> And I wanted to check if the scripts still generate an error message in a
> cron email and if they generate any extra statistical files.  If so, I have
> thought of another possible backwards-compatible idea but I haven't tried it
> out yet: what do you think of searching the default config file (and any
> file it includes) for a definition of SiteDomain, and only process it if
> that parameter is defined?

May be we can just disable "set -e" arround awstats commands?

> Just wanted to throw the idea out there for now--I will be away for three
> weeks on vacation and maybe when I get back I can try out the idea to see if
> it is feasible.  But maybe it won't even be necessary--I have yet to try out
> the latest changes.

Probably, you can even try 7.0 branch (some stuff from patches/ should
be dropped).