Re: [freesci-develop] Web page handling changes

[Max Horn]

Am 27.08.2007 um 19:48 schrieb Lars Skovlund:

> On Mon, Aug 27, 2007 at 11:14:05AM -0600, Christoph Reichenbach wrote:
> > )
> >
> > Max,
> >
> > On Mon, Aug 27, 2007 at 10:30:16AM +0200, Max Horn wrote:
> > > FYI, I can't completly check it out (and couldn't before your  
> > > changes
> > > either):
> > [...]
> >
> >   IWFH, so I'm afraid that I have no idea where that might be  
> > coming from :-/
> >
> >   I can checkpoint it; that might address the problem...?
>
> Please don't. That error message is the same one I was seeing until
> you reverted glutton to the uncheckpointed version. I haven't used the
> web repository apart from an initial checkout, so I'm afraid I have no
> other solutions to offer.

So, what would the solution be? It seems to me the repos is broken,  
as it seems impossible to make a fresh new checkout (or can any of  
you do that?). In the worst case, you might have to start it over  
from scratch (loosing the history), but that wouldn't be so bad,  
given that there are only 13 patches in it right now, would it?



> Am 27.08.2007 um 19:14 schrieb Christoph Reichenbach:
> > Max,
> >
> > On Mon, Aug 27, 2007 at 10:30:16AM +0200, Max Horn wrote:
[...]
>   Announcements/news are handled by a separate mechanism; all  
> project members
> have (or should have) logins/passwords that allow them to directly  
> post on the
> web page.

Excellent, and sounds more comfortable than what we have for ScummVM.
>   For the page itself I do have a manual update script, but it's  
> not set up in
> such a way that it would be easy to make it world-executable.  I'd  
> prefer an
> auto-upload after each commit, but the ftp web page upload takes  
> too long for
> this to be pleasant.

OK, sure.

Oh, and please note that my intention was *not* to suggest you guys  
shouldn't use a cron script! It certainly would never occur to me to  
even attempt to "dictate" what you guys should do :-).  I merely  
wanted to offset your original statement which sounded a bit as if  
using a cron job for this was the obvious "better" solution. Rather,  
it has advantages and drawbacks, and what's best depends on the needs  
of the given project. But you probably were aware of that anyway :).


Cheers,
Max