On Thu, 12 Aug 2021 16:24:33 -0400, Dennis Lee Bieber via fpc-pascal <fpc-pascal@lists.freepascal.org> wrote:
>On Thu, 12 Aug 2021 16:39:56 +0200, Bo Berglund via fpc-pascal ><fpc-pascal@lists.freepascal.org> declaimed >the following: > > >> >>Not verified by building fpc and lazarus on this machine yet. >>But it is clear that svn export is what should be in the script anyway to save >>both time and disk space... >> > > Based upon google searches; export is used to obtain the source file >tree but without maintaining version control on the fetched files. OTOH, co >creates a local SVN repository with a version control subdirectory, >metadata, etc., and working directory above it. I know this and that was the reason that I now tested both above. Note that I started version control life with CVS back in 2001 and there are no metadata in CVS except for a file listing the versioned files in the checkout including the revision. Export is the same as if one first does a checkout and then erase the hidden CVS directory in each folder. So the size difference between checkout and export in CVS is tiny, whereas both svn and git keeps huge data in parallel. > If you never intend to apply version control to the files -- and >download a complete new set of files for each change of interest then For the case I am asking there is ABSOLUTELY NO WISH to keep any metadata or possibility to update to newer revisions. Just the complete source file trees are required. -- Bo Berglund Developer in Sweden _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
