21.02.2011 22:40, davidMbrooke пишет: > On Tue, 2011-02-15 at 20:03 +0100, KP Kirchdoerfer wrote: >> Hi Andrew; >> >> Am Sonntag, 13. Februar 2011, um 22:45:13 schrieb Andrew: >>> P.S. I found that using of symlinks broke all packages with config files >>> into git (by default symlinks were copied) - now I fixed this (triveally >>> added -L option for cp for files from repository), so I'll run rebuild >>> of all tree from scratch, and then - push commit into git. >> It is my understanding that the difference between the download types "File" >> and "FileSymlink" are that files are copied with File.pm and linked with >> FileSymlink. >> >> The space a buildenv needs on a developers box isn't that different (5.8GB >> with FileSymlink, 5.9 GB with File - maybe your stats are different, but most >> the space in a buildenv is needed by the unpacked source packages which are >> not linkable). >> >> On the other hand it requires a different handling of config files provided >> in >> *our* source (cp -aL) compared to other files provided in the original source >> (cp -a) - which is somewhat error-prone. >> >> The way I work is to build seperate buildenvs to test different versions and >> changes. With FileSymlink I always work in the git repository (due to the >> links). >> >> If I want to avoid unnecessary downloads, I can change the type and >> serverpath >> in sources.cfg, tested File, FileSymlink, gitweb - and it all works (luckily >> the changes in buildtool.mk's for Filesymlink didn't break that). But the >> least intrusive way is IMHO to use download type File. >> >> Unless I missed a major point, I'd vote to revert the changes and to go with >> the DownloadTypes gitweb and File. >> >> kp > Hi kp, > > Like you I am having problems with our buildtool.mk files copying links > rather than the files they reference (e.g. for ".init" files). Sure, we > can fix by adding "-L" but that means changing many buildtool.mk files. It's already fixed in git one week ago. Except some packages (kismet, setserial, portmap) that I've fixed now/ > I would like to avoid the need to re-download the source files from > SourceForge, but I agree we can afford the space to copy from repo/ into > source/ rather than symlinking. > > Andrew: do you have a compelling reason to symlink rather than copy into > source/ ? > > dMb I don't like redundant file copying, also there is no need to copy modified files from sources dir into repository before commit, + it is no need to remove files from source after git update - it's enough to rebuild affected packages.
------------------------------------------------------------------------------ Index, Search & Analyze Logs and other IT data in Real-Time with Splunk Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. Free Software Download: http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
