What I usually do is create a daily CVS snapshot. I write up a script to
create it and package it up nicely in a .tar.gz to place it in the htdocs
directory. I pop this into the cron, and have it update once a day say
midnight. If you don't have enough space to keep previous snapshots, don't.
This usually suffices, but perhaps your development is moving so quickly
that this will still be considered far too outdated. You may wish to adjust
the time to match your expectations.
I was working on phpCVS which would have been a CVS client clone for
websites, but I've been slacking.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Kevin Lawton
Sent: Friday, November 24, 2000 10:09 AM
To: [EMAIL PROTECTED]
Subject: Re: .tar.gz - Packages available??
"Ph. Marek" wrote:
>
> Hi everybody,
>
> I'd like to test Plex86 on my machine but - there's only CVS access.
> I remember having seen a .tar.gz on the website (from march) - and looking
> into the cvs-page I'm being told about "snapshots every 2 weeks" available
> per FTP - but I can't find them.
I originally was thinking of snapshots periodically. Though
with such volatility in our development, about all that does
is offers out-of-date tarballs to people, who will then often
post out-of-date bugs to this list for problems which may have
been solved.
The best ideas I can think of are:
1) Is there a CVS web interface which will generate a tarball
from a given CVS server? That would be quite useful to serve
many OSS projects. This way any given version tag could be
retrieved, for people without CVS access.
2) Generate only one tarball (the latest CVS) and delete the others.
Seems like there ought to be a solution 1 around. If not, would
be a great project for someone.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Kevin Lawton [EMAIL PROTECTED]
MandrakeSoft, Inc. Plex86 developer
http://www.linux-mandrake.com/ http://www.plex86.org/
