Re: Source code control system
Hi the advantage of SVN over CVS is: 1. if you commit several files, in SVN it is an atomic action while in CVS it is not. Than mean that with CVS some file may be updated while other wont == your repository is not consistent 2. when renaming, CVS will loose the history while SVN whill handle it OK I think that the installasion of CVS is easier window client will depand on your development environment, for example you can get a plugin for Eclipse (one for CVS one for SVN) I also worked with WinCVS/CvsNT as a client for windows Have fun Shahar _ I am looking for old Vinyl record. If you have any that you don't need please mail me Thanks Shahar - Original Message - From: David Suna [EMAIL PROTECTED] To: linux-il@cs.huji.ac.il Sent: Monday, February 18, 2008 3:50 PM Subject: Source code control system I am interested in setting up a simple source code control system for a SOHO setup. There is a Linux server running Ubuntu that can act as the repository server. Clients would be Windows and Linux. I am looking for recommendations for a system that will be easy to set up and not have a steep learning curve (i.e. less than two hours to get the basic system up and running and configured). There will only be one or two people using the system to begin with and all access will be over the local network. Ideally, there would be a graphical or web based front end to administering the system and an easy to use client for both Windows and Linux. Any suggestions? -- David Suna [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
what about git? On Feb 19, 2008 8:16 PM, Shahar Dag [EMAIL PROTECTED] wrote: Hi the advantage of SVN over CVS is: 1. if you commit several files, in SVN it is an atomic action while in CVS it is not. Than mean that with CVS some file may be updated while other wont == your repository is not consistent 2. when renaming, CVS will loose the history while SVN whill handle it OK I think that the installasion of CVS is easier window client will depand on your development environment, for example you can get a plugin for Eclipse (one for CVS one for SVN) I also worked with WinCVS/CvsNT as a client for windows Have fun Shahar _ I am looking for old Vinyl record. If you have any that you don't need please mail me Thanks Shahar - Original Message - From: David Suna [EMAIL PROTECTED] To: linux-il@cs.huji.ac.il Sent: Monday, February 18, 2008 3:50 PM Subject: Source code control system I am interested in setting up a simple source code control system for a SOHO setup. There is a Linux server running Ubuntu that can act as the repository server. Clients would be Windows and Linux. I am looking for recommendations for a system that will be easy to set up and not have a steep learning curve (i.e. less than two hours to get the basic system up and running and configured). There will only be one or two people using the system to begin with and all access will be over the local network. Ideally, there would be a graphical or web based front end to administering the system and an easy to use client for both Windows and Linux. Any suggestions? -- David Suna [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
On Tuesday 19 February 2008, Shahar Dag wrote: Hi the advantage of SVN over CVS is: 1. if you commit several files, in SVN it is an atomic action while in CVS it is not. Than mean that with CVS some file may be updated while other wont == your repository is not consistent From what I know even the commit of one file in CVS is not atomic. Thus, a single file may be partially commited if something bad happens. In some other version control systems, such as ClearCase, each file is commited atomically, while the transcation itself is not atomic. In Subversion, however, and in most other modern open-source version control systems, the entire commit transaction is atomic. 2. when renaming, CVS will loose the history while SVN whill handle it OK Yes. Note, however, that at the moment svn will not merge diffs against files that were renamed afterwards. Aside from these, svn has many other advantages over CVS. See the Subversion's Features list in http://subversion.tigris.org/ . Regards, Shlomi Fish - Shlomi Fish [EMAIL PROTECTED] Homepage:http://www.shlomifish.org/ I'm not an actor - I just play one on T.V. To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
Ohad Levy wrote: what about git? Git main attraction is distributed development. For something like the Linux kernel it is indispensable. The thing is, most software development, even in the Open Source world, is not really distributed. Also, I don't think there is a Windows git client :-) Gilad = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
svn (subversion) is relatively easy to use and has both gui and cli frontends (windows maybe only gui). there is tortoise svn which integrates into explorer. cvs is mostly the same. The big difference is that with cvs commits are per file (if you made dependent changes on two different files the commit won't show it). cvs also doesn't support renaming (it's the same as deleting the file and importing a new one). svn commits as a group, i.e you can commit changes to several files as a group. For better and worse (mostly space) svn keeps a copy of the pull also locally (you basically have two copies of the code), although I don't think you can commit against the local copy, just see what changes you made. On the other hand cvs is older, and thus has a bit more software supporting it (that is not as true nowadays). Other options are tls (arch) which I know little about, and git. git is mostly command line (I found the gui tools to be very limited), although the learning curve for committing is mostly ok. It also relies on some linux filesystem abilities, so it will run on windows but requires msys. It's big difference is that it is a distributed system where each use maintains a complete copy of the repository and can commit locally as much as he/she wants with zero network overhead, when you are happy you can push the changes to a central repository. I like it since it allows you to work on your own stuff until it's ready for the repository without losing the ability to keep a commit track (although you can achieve the same end with branches, as long as you are always connected to the server, a thing that git doesn't require). It was built with the kernel development cycle in mind. Bottom line, for a SOHO that doesn't require offline commits and wants a low learning curve solution I would recommend svn. cvs is too old and doesn't allow atomic commits, git is too radical for most development environments and arch I know nothing about (I think that it has the same lack of tools as git) On Mon, 18 Feb 2008 16:05:44 +0200 Maxim Kudelya [EMAIL PROTECTED] wrote: David Suna wrote: I am interested in setting up a simple source code control system for a SOHO setup. .. Any suggestions? You could use Subversion (http://subversion.tigris.org/) as version control system, Trac (http://trac.edgewall.org/) as web-based front end and TortoiseSVN (http://tortoisesvn.net/) as Windows client. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
On Tue, Feb 19, 2008 at 02:16:39PM +0200, Shahar Dag wrote: Hi the advantage of SVN over CVS is: 1. if you commit several files, in SVN it is an atomic action while in CVS it is not. Than mean that with CVS some file may be updated while other wont == your repository is not consistent 2. when renaming, CVS will loose the history while SVN whill handle it OK I think that the installasion of CVS is easier With svn you can still work with an equivalent server-less files / svn+ssh mode. The problem is that you can't simply set per-directory permissions as simply as you can with CVS. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
On Tue, 19 Feb 2008 16:21:56 +0200 Gilad Ben-Yossef [EMAIL PROTECTED] wrote: Ohad Levy wrote: what about git? Git main attraction is distributed development. For something like the Linux kernel it is indispensable. The thing is, most software development, even in the Open Source world, is not really distributed. Also, I don't think there is a Windows git client :-) It does run well within msys (did it for a while). the kde interface should compile also, but it gave me trouble when I tried it a few months back. didn't have to fiddle with it though to check if it's simple to solve. Gilad = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
Oi, Git is a silly that. M - Ohad Levy [EMAIL PROTECTED] wrote: what about git? -- ---MAV Marc A. Volovic Swiftouch, LTD [EMAIL PROTECTED] +972-544-676764 = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
On Tuesday 19 February 2008, Gilad Ben-Yossef wrote: Ohad Levy wrote: what about git? Git main attraction is distributed development. For something like the Linux kernel it is indispensable. The thing is, most software development, even in the Open Source world, is not really distributed. Also, I don't think there is a Windows git client :-) Actually, there is a git client for cygwin, which should be pretty good. Also, Adam Kennedy here reports (unfavourably) on the native Win32 git: http://use.perl.org/~Alias/journal/33825 But that put aside - yes, if you're concerned with Win32 compatibility, then git may have a problem in this regard. Cheers, Shlomi Fish - Shlomi Fish [EMAIL PROTECTED] Homepage:http://www.shlomifish.org/ I'm not an actor - I just play one on T.V. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
On Mon, 18 Feb 2008 17:57:32 +0200 Shachar Shemesh [EMAIL PROTECTED] wrote: Marc Volovic wrote: Good heavens... Subversion and/or CVS - take your choice. I'll go with that recommendation if you only give me one thing that CVS does better than SVN. Between the two, I fail to find a single reason to prefer the former over the later. One of your lines is wrong, I guess from the first line that you meant I fail to find a single reason to prefer the later over the former. the only reason I can think of currently is that svn stores an extra local repository cvs does everything remotely (only one local copy). If you have a big tree and not enough local space (should be an issue with modern hard disk, used to be more of an issue a few years back). I believe that svn is mature enough so you don't have to worry about the track record. Shachar = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
On Tuesday 19 February 2008, Ohad Levy wrote: what about git? Well, my take on the problems with git are that: 1. Its Windows-support may be lacking. See: http://use.perl.org/~Alias/journal/33825 2. It is more complex than Subversion: shlomi:~$ git- Display all 132 possibilities? (y or n) 3. The command line syntax of operating it, should be less CVS-like and less intuitve than Subversion's. 4. Possibly have some gotchas that are not present in Subversion. Like no support for keywords: http://www.mail-archive.com/haifux%40haifux.org/msg02971.html -- git should be a fine version control system, but Subversion may be good enough or better for the usecase of the OP. Regards, Shlomi Fish On Feb 19, 2008 8:16 PM, Shahar Dag [EMAIL PROTECTED] wrote: Hi the advantage of SVN over CVS is: 1. if you commit several files, in SVN it is an atomic action while in CVS it is not. Than mean that with CVS some file may be updated while other wont == your repository is not consistent 2. when renaming, CVS will loose the history while SVN whill handle it OK I think that the installasion of CVS is easier window client will depand on your development environment, for example you can get a plugin for Eclipse (one for CVS one for SVN) I also worked with WinCVS/CvsNT as a client for windows Have fun Shahar _ I am looking for old Vinyl record. If you have any that you don't need please mail me Thanks Shahar - Original Message - From: David Suna [EMAIL PROTECTED] To: linux-il@cs.huji.ac.il Sent: Monday, February 18, 2008 3:50 PM Subject: Source code control system I am interested in setting up a simple source code control system for a SOHO setup. There is a Linux server running Ubuntu that can act as the repository server. Clients would be Windows and Linux. I am looking for recommendations for a system that will be easy to set up and not have a steep learning curve (i.e. less than two hours to get the basic system up and running and configured). There will only be one or two people using the system to begin with and all access will be over the local network. Ideally, there would be a graphical or web based front end to administering the system and an easy to use client for both Windows and Linux. Any suggestions? -- David Suna [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED] -- - Shlomi Fish [EMAIL PROTECTED] Homepage:http://www.shlomifish.org/ I'm not an actor - I just play one on T.V. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Source code control system
I am interested in setting up a simple source code control system for a SOHO setup. There is a Linux server running Ubuntu that can act as the repository server. Clients would be Windows and Linux. I am looking for recommendations for a system that will be easy to set up and not have a steep learning curve (i.e. less than two hours to get the basic system up and running and configured). There will only be one or two people using the system to begin with and all access will be over the local network. Ideally, there would be a graphical or web based front end to administering the system and an easy to use client for both Windows and Linux. Any suggestions? -- David Suna [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
David Suna wrote: I am interested in setting up a simple source code control system for a SOHO setup. .. Any suggestions? You could use Subversion (http://subversion.tigris.org/) as version control system, Trac (http://trac.edgewall.org/) as web-based front end and TortoiseSVN (http://tortoisesvn.net/) as Windows client. -- maxym = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
CVS or SVN are pretty straight forward. Most IDEs have integration with them. Both have nice windows shell extensions (TortoiseSVN/CVS) http://www.nongnu.org/cvs/ http://subversion.tigris.org/ Regards Alex Dover On Feb 18, 2008 3:50 PM, David Suna [EMAIL PROTECTED] wrote: I am interested in setting up a simple source code control system for a SOHO setup. There is a Linux server running Ubuntu that can act as the repository server. Clients would be Windows and Linux. I am looking for recommendations for a system that will be easy to set up and not have a steep learning curve (i.e. less than two hours to get the basic system up and running and configured). There will only be one or two people using the system to begin with and all access will be over the local network. Ideally, there would be a graphical or web based front end to administering the system and an easy to use client for both Windows and Linux. Any suggestions? -- David Suna [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
Good heavens... Subversion and/or CVS - take your choice. I am not sure what you mean by graphic management, but both have graphic and web CLIENTS. Management is something completely different :-). Me = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
On Monday 18 February 2008, Maxim Kudelya wrote: David Suna wrote: I am interested in setting up a simple source code control system for a SOHO setup. .. Any suggestions? You could use Subversion (http://subversion.tigris.org/) as version control system, Trac (http://trac.edgewall.org/) as web-based front end and TortoiseSVN (http://tortoisesvn.net/) as Windows client. I can also recommend Subversion. I've been using it for several years now, and like it. Note that I may be a bit biased because I contributed some code to Subversion. There are other systems: * http://en.wikipedia.org/wiki/List_of_revision_control_software * http://better-scm.berlios.de/ But most of the other open-source version control systems are distributed. Regards, Shlomi Fish - Shlomi Fish [EMAIL PROTECTED] Homepage:http://www.shlomifish.org/ I'm not an actor - I just play one on T.V. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
Marc Volovic wrote: Good heavens... Subversion and/or CVS - take your choice. I'll go with that recommendation if you only give me one thing that CVS does better than SVN. Between the two, I fail to find a single reason to prefer the former over the later. Shachar = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Source code control system
Shachar Shemesh wrote: I'll go with that recommendation if you only give me one thing that CVS does better than SVN. Between the two, I fail to find a single reason to prefer the former over the later. Well, given that subversion was written to be an improved replacement for CVS, it's unlikely that CVS would do anything better than subversion does it unless you happen to find a feature that the subversion authors call an improvement that you personally feel is a backward step. Geoff. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
