|
From: Julian S. <bel...@gm...> - 2008-08-20 17:32:15
|
R. Reucher pisze: > On Wed August 20 2008 15:27, Julian Sikorski wrote: >> The rsync issue turned out to be caused by old glibc/kernel being >> installed on the builder. > So you were able to fix it?! > > Regarding "rsync" or plain "install"... there's always the possibility to > change that in the OS- and/or distribtion-configuration: > > rene@thunder:~/src/qmc2> cat arch/default.cfg > QMAKE = qmake > LUPDATE = lupdate > LRELEASE = lrelease > MAKE = make > MKDIR = mkdir -p > RM = rm -f > LN = ln > RMDIR = rmdir > TIME = time > CD = cd > CP = cp > RSYNC = rsync -rlpt > DATE = date +%Y%m%d%H%M%S > SED = sed > COLRM = colrm > AWK = awk > FIND = find > GREP = grep > TAR = tar > OSNAME = $(ARCH) > BASENAME = basename > > And yes, I 'm using "rsync -rlpt" because it's the only platform independent > solution I found to cleanly support symbolic links. For cp we could > uses --no-derefence, but only in case of the GNU version... "install" isn't > always the same as well, so I can't tell what happens on non-GNU POSIX > environments... but I could try to figure out what has been used for the > install by Qt itself (should be part of the mkspec) and use that instead > perhaps... another option would be to write a built in "install" program > based on Qt. Probably the best solution, because that would > work "everywhere". > > Have fun, René The solution would be to use rsync -rpt or rsync -rlp, we still have not decided what is better. It seems that on older systems you cannot set timestamp of a symlink and rsync 2.6.9 does not handle that very well. Regards, Julian |
