Author Topic: Move repository to subversion?  (Read 19696 times)

anonuser

  • Guest
Re: Move repository to subversion?
« Reply #15 on: November 18, 2005, 11:47:10 pm »
its free for opensource projects.
You're required to submit your licence and project description to them but Code::Blocks is pretty well known so I doubt they'll question anything..

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: Move repository to subversion?
« Reply #16 on: November 18, 2005, 11:51:17 pm »
But you need a server, and this will cost on the order of $50-100 monthly, depending on the amount of traffic.

Also, perforce has a major usability disadvantage in regard of svn and cvs. Everybody is familiar with cvs and svn, and everybody has the tools on his PC. This is not true for perforce.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

anonuser

  • Guest
Re: Move repository to subversion?
« Reply #17 on: November 18, 2005, 11:53:15 pm »
http://www.perforce.com/perforce/opensource-faq.html

This is what you need to know.

Perforce is super powerful and has amazing integration in the IDEs MS DEV studio plugin is amazing.
I use it at my place of work and wouldn't do source control without it.

anonuser

  • Guest
Re: Move repository to subversion?
« Reply #18 on: November 18, 2005, 11:54:24 pm »
Well its not all that different. Esepcially since there are easy to ues graphical tools provided by Perforce for almost any OS. Linux, *BSD, Unix, Win32. All use the same software.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: Move repository to subversion?
« Reply #19 on: November 19, 2005, 12:19:35 am »
TortoiseProc is the GUI part of TortoiseSVN.
Sorry, I don't get it: Does this mean that TortoiseSVN does finally have a standalone GUI without shell inegration? Maybe I should give it a try again...?!

Morten.

Ps.: Sorry, I know, it does not belong into this thread.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: Move repository to subversion?
« Reply #20 on: November 19, 2005, 03:38:39 pm »
TortoiseSVN consists of 4 major parts:
1. An improved version of plink which you can use as standalone replacement
2. The Windows Explorer integration hack. This does little but build a popup menu and draw some fancy colours.
3. TortoiseProc which is called by the Explorer thingie. It does the "real" GUI stuff and the actual work.
4. TortoiseMerge, a standalone Diff/Merge application

You can call TortoiseProc from either a shell or from a selfmade little wrapper program, or you could make a shortcut to TortoiseProc with a commandline switch telling it what action to perform.
Either way, it will then present you with the well-known TortoiseSVN GUI, so you can select what to checkout or what to update.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9723
Re: Move repository to subversion?
« Reply #21 on: November 19, 2005, 04:54:19 pm »
You can call TortoiseProc from either a shell or from a selfmade little wrapper program,
or you could make a shortcut to TortoiseProc with a commandline switch telling it what action to perform.
Aaah, I didn't know that. Now I have downloaded and installed TortoiseSVN to give it a try. I found the /command:[...] documentation to read how to do stuff. It's nice, but there is a drawback (for me): Every path seems to have be provided per command line. As you said: One would be required to write a wrapper. Making shortcuts would result in an awful lot of shortcuts depending on what repositry, sandbox, operation etc...
I guess I still have to wait for a suitable "pure" stand-alone product... :(

Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ