On 12/11/06, Vincent Snijders <[EMAIL PROTECTED]> wrote:
George Birbilis schreef:
>> All this is possible, but IMHO it is nonsense to put effort
>> into creating such a snapshot.
>>
>> I think there is some intelligence test, test if people
>> persevere enough. If a person cannot find the link to getting
>> the sources from the home page and follow those instructions
>> to get a svn checkout, it is unreasonable to expect such a
>> person to provide sensible patches.
>
> I can't say I agree, people with experience and skills don't have the time
> to spend reading all those instructions etc. So they must be very determined
> to fix or enhance something that bugs them in Lazarus or if they like very
> much to contribute something back to Lazarus. In both cases the time they
> lose in setting this up (if they don't get discouraged and give up in the
> first place) is lost from time they'd give in reading the sourcecode and
> possible fixes/enhanchements they'd do (and contribute).
Maybe, maybe not.
>
> Regarding size, we could have a clever autodownloader/installer that reads a
> config/instructions file online from Laz site and grabs the correct FPC
> archive from FPC site, unpacks it etc., same with Laz files and places them
> were needed
Yes, please implement this. I cannot wait for your patches, because I have been
dreaming for something like this for two years now and I never seem to come to
it,
there always thinks I like to do more or find to be more missing in Lazarus.
> Regarding the .svn folder I believe if it's standard it should be in the
> snapshot (it doesn't take much size after all) so that one can go on and use
> the SVN after they initially get a snapshot (for quickstarting)
It is standardized for all platforms, but not for all versions. For example, if
I
created the sub directory with svn 1.4, you cannot read it with svn 1.3.
The .svn directories would certainly double the size of the snapshot. The
size of the .svn directories is the price paid for being able to do
'svn status' ,
'svn diff' without touching the server.
However, snapshots can only be updated by downloading a newer one - which
is a big disadvantage because of their size.
Using the svn version is much more convenient than the snapshots because
updating is way cheaper .
On the other hand, it would be nice to have an "Update Lazarus" option
in the menu
for synchronizing the files that exists on the local machine with
those that exist on
a server . This functionality would be configurable to allow choosing between
updating to the latest development version or to the stable version(s).
I'm thinking about something similar to rsync (that can synchronize a
local directory with a remote one with minimal data transfer : it
only transfers
the modifications ). Unfortunately (as far as i know) rsync is not truly
cross-platform : some time ago when i needed a rsync client for windows i found
only one based on the cygwin emulation.
But it doesn't seem to be extremely hard to build something like :
- the Lazarus tree is put on a ftp server
- inside the tree there is a file containing (for axemple) the list of
files and their md5 checksums
- when a user clicks "Update Lazarus" , the program downloads the list of files
and compares it to what exists on the local machine. And then downloads
the files that were added or modified.
Probably this is just an idea for the future : for Lazarus 1.0 and
beyond ? Right now
Lazarus is under active development and updating through svn works just fine in
my opinion .
Cheers,
Adrian Maier
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
