Talk:EMU - Revision history

Barnski at 22:33, 21 April 2006

2006-04-21T22:33:46Z

Barnski at 18:11, 21 April 2006

2006-04-21T18:11:48Z

Barnski at 18:11, 21 April 2006

2006-04-21T18:11:35Z

Barnski at 18:10, 21 April 2006

2006-04-21T18:10:36Z

Patrickr at 16:11, 21 April 2006

2006-04-21T16:11:41Z

New page

'''[[User:Patrickr|Patrickr]] 18:11, 21 April 2006 (CEST)'''

Do you plan to write your own repository system? I think it would be nicer if you could support already existing repositories like Subversion.

← Older revision		Revision as of 22:33, 21 April 2006
Line 8:		Line 8:
	We plan to make our own server, that will handle the code repository. If we were to use subversion as server we would fail our project goal: to provide more functionality than the current solutions. Although we do not know the full capacities of svn, I think it would not allow us to handle code synchronisation on a locking-base, where possibly not only whole classes are lockable, but also features.		We plan to make our own server, that will handle the code repository. If we were to use subversion as server we would fail our project goal: to provide more functionality than the current solutions. Although we do not know the full capacities of svn, I think it would not allow us to handle code synchronisation on a locking-base, where possibly not only whole classes are lockable, but also features.
	Nevertheless we will make sure that we design our components in a way to guarantee maximal reusability, such that the emu-client could be replaced by a svn-client for example.		Nevertheless we will make sure that we design our components in a way to guarantee maximal reusability, such that the emu-client could be replaced by a svn-client for example.
		+
		+	Maybe this quote helps to distinguish emu from svn:
		+	"What is SVN?"
		+	[...]
		+	"Some version control systems are also software configuration management (SCM) systems. These systems are specifically tailored to manage trees of source code, and have many features that are specific to software development—such as natively understanding programming languages, or supplying tools for building software. Subversion, however, is not one of these systems. It is a general system that can be used to manage any collection of files. For you, those files might be source code—for others, anything from grocery shopping lists to digital video mixdowns and beyond."
		+
		+	-from http://svnbook.red-bean.com
		+
		+	Consider EMU as such a SCM system.

@@ Line 2: / Line 2: @@
 Do you plan to write your own repository system? I think it would be nicer if you could support already existing repositories like Subversion.
 '''[[User:Barnski|Bernhard Buss]] 20:05, 21 April 2006 (GMT+1)'''
 We plan to make our own server, that will handle the code repository. If we were to use subversion as server we would fail our project goal: to provide more functionality than the current solutions. Although we do not know the full capacities of svn, I think it would not allow us to handle code synchronisation on a locking-base, where possibly not only whole classes are lockable, but also features.
 Nevertheless we will make sure that we design our components in a way to guarantee maximal reusability, such that the emu-client could be replaced by a svn-client for example.

@@ Line 3: / Line 3: @@
 Do you plan to write your own repository system? I think it would be nicer if you could support already existing repositories like Subversion.
 We plan to make our own server, that will handle the code repository. If we were to use subversion as server we would fail our project goal: to provide more functionality than the current solutions. Although we do not know the full capacities of svn, I think it would not allow us to handle code synchronisation on a locking-base, where possibly not only whole classes are lockable, but also features.
 Nevertheless we will make sure that we design our components in a way to guarantee maximal reusability, such that the emu-client could be replaced by a svn-client for example.

← Older revision		Revision as of 18:10, 21 April 2006
Line 2:		Line 2:

	Do you plan to write your own repository system? I think it would be nicer if you could support already existing repositories like Subversion.		Do you plan to write your own repository system? I think it would be nicer if you could support already existing repositories like Subversion.
		+
		+	We plan to make our own server, that will handle the code repository. If we were to use subversion as server we would fail our project goal: to provide more functionality than the current solutions. Although we do not know the full capacities of svn, I think it would not allow us to handle code synchronisation on a locking-base, where possibly not only whole classes are lockable, but also features.
		+	Nevertheless we will make sure that we design our components in a way to guarantee maximal reusability, such that the emu-client could be replaced by a svn-client for example.