Reduce Subversion pristine copy - Historie editací

Chronos v 27. 7. 2022, 17:20

2022-07-27T17:20:16Z

← Starší verze		Verze z 27. 7. 2022, 19:20
Řádek 48:		Řádek 48:
	* [http://bazaar.canonical.com Bazaar] - can work in client-server mode and checkout just single copy of files. Not developed anymore.		* [http://bazaar.canonical.com Bazaar] - can work in client-server mode and checkout just single copy of files. Not developed anymore.
	* [https://github.com/robehickman/BVersion BVersion] - a centralised version control system for managing binary files like images, audio, and video.		* [https://github.com/robehickman/BVersion BVersion] - a centralised version control system for managing binary files like images, audio, and video.
			* [https://github.com/mekberg/boar Boar VCS]

	=External links=		=External links=

Chronos v 27. 7. 2022, 17:11

2022-07-27T17:11:06Z

← Starší verze		Verze z 27. 7. 2022, 19:11
Řádek 47:		Řádek 47:
	* [http://www.nongnu.org/cvs/ CVS] - old predecessor of Subversion		* [http://www.nongnu.org/cvs/ CVS] - old predecessor of Subversion
	* [http://bazaar.canonical.com Bazaar] - can work in client-server mode and checkout just single copy of files. Not developed anymore.		* [http://bazaar.canonical.com Bazaar] - can work in client-server mode and checkout just single copy of files. Not developed anymore.
			* [https://github.com/robehickman/BVersion BVersion] - a centralised version control system for managing binary files like images, audio, and video.

	=External links=		=External links=

	* [http://vcs.atspace.co.uk/2012/06/20/missing-pristines-in-svn-working-copy/ Missing pristine files in SVN working copy]		* [http://vcs.atspace.co.uk/2012/06/20/missing-pristines-in-svn-working-copy/ Missing pristine files in SVN working copy]

Chronos v 28. 1. 2022, 15:22

2022-01-28T15:22:23Z

← Starší verze		Verze z 28. 1. 2022, 17:22
Řádek 24:		Řádek 24:
	It maybe possible to temporary make pristine file empty and update their content manually by invoking some helper program. Such program could check svn status and download correct content of modified files from repository to be able to commit them. Set zero size to other pristine files. The program should be able to work with SVN sqlite database to read file name to pristine name relation. Also it should be multi-platform.		It maybe possible to temporary make pristine file empty and update their content manually by invoking some helper program. Such program could check svn status and download correct content of modified files from repository to be able to commit them. Set zero size to other pristine files. The program should be able to work with SVN sqlite database to read file name to pristine name relation. Also it should be multi-platform.

			zero-pristine.sh:
	<source lang="bash">		<source lang="bash">
	#!/bin/bash		#!/bin/bash

			CWD=$(pwd)
⚫	for F in $(find ./.svn/pristine -type f -size +0);
			let "i=0"
		⚫	for F in $(find $CWD/.svn/pristine -name *.svn-base -type f -size +0);
	do		do
			chmod 666 $F
	cat /dev/null >$F		cat /dev/null >$F
			chmod 444 $F
			let "i+=1"
	done		done

			echo "$i svn pristine files zeroed"
	</source>		</source>
	If pristine files are set to empty then all svn operation could be used except these related to file content as svn diff or svn commit of modified files. To be able also work with file diff, pristine file content should be restored from repository somehow.		If pristine files are set to empty then all svn operation could be used except these related to file content as svn diff or svn commit of modified files. To be able also work with file diff, pristine file content should be restored from repository somehow.

Chronos v 25. 10. 2015, 17:15

2015-10-25T17:15:41Z

← Starší verze		Verze z 25. 10. 2015, 19:15
Řádek 14:		Řádek 14:
	==File deduplication of working copy==		==File deduplication of working copy==

	It could possibly work on file system level with existing file systems or as virtual file system. But file deduplication on system level need more CPU power and more memory. There are also some copy-on-write file systems which could be usable if subversion client would make copy of file by using system service function for copying. ~~Such~~ ~~file~~ ~~system~~ is for example [https://btrfs.wiki.kernel.org/index.php/Main_Page Btrfs]		It could possibly work on file system level with existing file systems or as virtual file system. But file deduplication on system level need more CPU power and more memory. There are also some copy-on-write file systems which could be usable if subversion client would make copy of file by using system service function for copying. Close to such idea is for example [https://btrfs.wiki.kernel.org/index.php/Main_Page Btrfs] but it uses copy-on-write for different purpose. To avoid losing data during power outage thanks to that new data are not overwritten over old data but written to different place.

	One example could be [http://scord.sourceforge.net/ Scord] which solves this for versions <= 1.6 on Linux platform.		One example could be [http://scord.sourceforge.net/ Scord] which solves this for versions <= 1.6 on Linux platform.

Chronos v 25. 10. 2015, 16:29

2015-10-25T16:29:03Z

← Starší verze		Verze z 25. 10. 2015, 18:29
Řádek 1:		Řádek 1:
	Subversion VCS stores copy of each file in pristine directory (formerly called textbase) located in hidden .svn directory in working copy root directory. Storing copy for every file means that working copy takes twice as much size as stored files. This may not be problem for small repository but if you want to store for example ~~30GB~~ of photos in repository and want to checkout working copy on machine with 60 GB drive then you have a problem.		Subversion VCS stores copy of each file in pristine directory (formerly called textbase) located in hidden .svn directory in working copy root directory. Storing copy for every file means that working copy takes twice as much size as user stored files alone. This may not be problem for small repository but if you want to store for example 30 GB of photos, music, video or other big binary files in repository and want to checkout working copy on machine with just 60 GB or smaller drive then you have a problem. Also during checkout twice as content size is written to disk which lead to higher disk load.

	Also this slows down every checkout as two copies of downloaded files needed to be created on filesystem instead one.		Also this slows down every checkout as two copies of downloaded files needed to be created on filesystem instead one.
Řádek 14:		Řádek 14:
	==File deduplication of working copy==		==File deduplication of working copy==

	It could possibly work on ~~filesystem~~ level with existing ~~filesystems~~ or as virtual ~~filesystem~~. But file deduplication on system level need more CPU power and more memory. There are also some copy-on-write file systems which could be usable if subversion client would make copy of file by using system service function for copying.		It could possibly work on file system level with existing file systems or as virtual file system. But file deduplication on system level need more CPU power and more memory. There are also some copy-on-write file systems which could be usable if subversion client would make copy of file by using system service function for copying. Such file system is for example [https://btrfs.wiki.kernel.org/index.php/Main_Page Btrfs]

	One example could be [http://scord.sourceforge.net/ Scord] which solves this for versions <= 1.6 on Linux platform.		One example could be [http://scord.sourceforge.net/ Scord] which solves this for versions <= 1.6 on Linux platform.

			Theoretically file system with deduplication support could be used. This could be realized under Linux as file mounted as loop device. [https://en.wikipedia.org/wiki/ZFS#Deduplication ZFS] file system support deduplication but it is not part of Linux kernel.

	==Make pristine files zero size by helper program==		==Make pristine files zero size by helper program==

	It maybe possible to temporary make pristine file empty and update their content manually by invoking some helper program. Such program could check svn status and download correct content of modified files from repository to be able to commit them. Set zero size to other pristine files. The program should be able to work with ~~svn~~ sqlite database to read file name to pristine name relation. Also it should be multi-platform.		It maybe possible to temporary make pristine file empty and update their content manually by invoking some helper program. Such program could check svn status and download correct content of modified files from repository to be able to commit them. Set zero size to other pristine files. The program should be able to work with SVN sqlite database to read file name to pristine name relation. Also it should be multi-platform.

	<source lang="bash">		<source lang="bash">
Řádek 34:		Řádek 36:
	=Alternative VCS=		=Alternative VCS=

	Unfortunately there not many other VCS systems which can download just single copy of files in checkout.		Unfortunately there are not many other VCS systems which can download just single copy of files during checkout.
	* CVS - old predecessor of Subversion		* [http://www.nongnu.org/cvs/ CVS] - old predecessor of Subversion
	* ~~Bazzar~~ - can work in client-server mode and checkout just single copy of files. Not developed anymore.		* [http://bazaar.canonical.com Bazaar] - can work in client-server mode and checkout just single copy of files. Not developed anymore.

	=External links=		=External links=

Chronos v 16. 10. 2015, 21:39

2015-10-16T21:39:44Z

← Starší verze		Verze z 16. 10. 2015, 23:39
Řádek 1:		Řádek 1:
	Subversion VCS stores copy of each file in pristine directory (formerly called textbase) located in hidden .svn directory in working copy root directory. Storing copy for every file means that working copy takes twice as much size as stored files. This may not be problem for small repository but if you want to store for example 30GB of photos in repository and want to checkout working copy on machine with 60 GB drive then you have a problem.		Subversion VCS stores copy of each file in pristine directory (formerly called textbase) located in hidden .svn directory in working copy root directory. Storing copy for every file means that working copy takes twice as much size as stored files. This may not be problem for small repository but if you want to store for example 30GB of photos in repository and want to checkout working copy on machine with 60 GB drive then you have a problem.

			Also this slows down every checkout as two copies of downloaded files needed to be created on filesystem instead one.

	=Possible methods of reducing pristine size=		=Possible methods of reducing pristine size=
Řádek 29:		Řádek 31:
	</source>		</source>
	If pristine files are set to empty then all svn operation could be used except these related to file content as svn diff or svn commit of modified files. To be able also work with file diff, pristine file content should be restored from repository somehow.		If pristine files are set to empty then all svn operation could be used except these related to file content as svn diff or svn commit of modified files. To be able also work with file diff, pristine file content should be restored from repository somehow.

			=Alternative VCS=

			Unfortunately there not many other VCS systems which can download just single copy of files in checkout.
			* CVS - old predecessor of Subversion
			* Bazzar - can work in client-server mode and checkout just single copy of files. Not developed anymore.

	=External links=		=External links=

Chronos v 16. 10. 2015, 21:34

2015-10-16T21:34:10Z

← Starší verze		Verze z 16. 10. 2015, 23:34
Řádek 1:		Řádek 1:
	Subversion VCS stores copy of each file in pristine directory located in hidden .svn directory in working copy root directory. Storing copy for every file means that working copy takes twice as much size as stored files. This may not be problem for small repository but if you want to store for example 30GB of photos in repository and want to checkout working copy on machine with 60 GB drive then you have a problem.		Subversion VCS stores copy of each file in pristine directory (formerly called textbase) located in hidden .svn directory in working copy root directory. Storing copy for every file means that working copy takes twice as much size as stored files. This may not be problem for small repository but if you want to store for example 30GB of photos in repository and want to checkout working copy on machine with 60 GB drive then you have a problem.

	=Possible methods of reducing pristine size=		=Possible methods of reducing pristine size=

Chronos v 16. 10. 2015, 21:33

2015-10-16T21:33:15Z

← Starší verze		Verze z 16. 10. 2015, 23:33
Řádek 1:		Řádek 1:
	Subversion VCS ~~store~~ copy of each file pristine directory ~~placed~~ in ~~own~~ hidden .svn directory. Storing copy for ~~each~~ file means that working copy takes twice as much size as stored files. This may not be problem for small repository but if you want to store for example 30GB of photos in repository and want to checkout working copy on machine with 60 GB drive then you have problem.		Subversion VCS stores copy of each file in pristine directory located in hidden .svn directory in working copy root directory. Storing copy for every file means that working copy takes twice as much size as stored files. This may not be problem for small repository but if you want to store for example 30GB of photos in repository and want to checkout working copy on machine with 60 GB drive then you have a problem.

	=Possible methods of reducing pristine size=		=Possible methods of reducing pristine size=

Chronos v 16. 10. 2015, 21:30

2015-10-16T21:30:17Z

← Starší verze		Verze z 16. 10. 2015, 23:30
Řádek 5:		Řádek 5:
	==Subversion client built-in mechanism==		==Subversion client built-in mechanism==

	The feature could be implemented directly to the client in some later 1.8+ version.		The feature could be implemented directly to the client in some later 1.9+ version.

	There is already opened [http://subversion.tigris.org/issues/show_bug.cgi?id=525 Issue 525] named "allow working copies without text-base/".		There is already opened [http://subversion.tigris.org/issues/show_bug.cgi?id=525 Issue 525] named "allow working copies without text-base/".
Řádek 14:		Řádek 14:
	It could possibly work on filesystem level with existing filesystems or as virtual filesystem. But file deduplication on system level need more CPU power and more memory. There are also some copy-on-write file systems which could be usable if subversion client would make copy of file by using system service function for copying.		It could possibly work on filesystem level with existing filesystems or as virtual filesystem. But file deduplication on system level need more CPU power and more memory. There are also some copy-on-write file systems which could be usable if subversion client would make copy of file by using system service function for copying.

	One example could be [http://scord.sourceforge.net/ Scord] which ~~solve~~ this for versions <= 1.6 on Linux platform		One example could be [http://scord.sourceforge.net/ Scord] which solves this for versions <= 1.6 on Linux platform.

	==Make pristine files zero size by helper program==		==Make pristine files zero size by helper program==

	It maybe possible to temporary make pristine file empty and update their content manually by invoking ~~come~~ helper program. Such program could check svn status and download correct content of modified files from repository to be able to commit them. Set zero size to other pristine files. ~~Such~~ program should be able to work with svn sqlite database to read file name to pristine name relation. Also it should be multi-platform.		It maybe possible to temporary make pristine file empty and update their content manually by invoking some helper program. Such program could check svn status and download correct content of modified files from repository to be able to commit them. Set zero size to other pristine files. The program should be able to work with svn sqlite database to read file name to pristine name relation. Also it should be multi-platform.

	<source lang="bash">		<source lang="bash">

Chronos v 25. 11. 2014, 21:50

2014-11-25T21:50:01Z

← Starší verze		Verze z 25. 11. 2014, 23:50
Řádek 12:		Řádek 12:
	==File deduplication of working copy==		==File deduplication of working copy==

	It could possibly work on filesystem level with existing filesystems or as virtual filesystem.		It could possibly work on filesystem level with existing filesystems or as virtual filesystem. But file deduplication on system level need more CPU power and more memory. There are also some copy-on-write file systems which could be usable if subversion client would make copy of file by using system service function for copying.

	One example could be [http://scord.sourceforge.net/ Scord] which solve this for versions <= 1.6 on Linux platform		One example could be [http://scord.sourceforge.net/ Scord] which solve this for versions <= 1.6 on Linux platform