Page 1 of 2
Is there any reason to keep the CVS repository?
Posted: 23.03.2008, 19:44
by ajtribick
The Celestia project page on Sourceforge.net lists both the SVN and CVS repositories - surely if the development is now happening on SVN, the CVS repository should be removed?
Re: Is there any reason to keep the CVS repository?
Posted: 23.03.2008, 19:58
by chris
ajtribick wrote:The Celestia project page on Sourceforge.net lists both the SVN and CVS repositories - surely if the development is now happening on SVN, the CVS repository should be removed?
I don't think that there's a reason to keep it. I just removed it from the 'Code' menu on the SourceForge page, though the CVS repository still exists. If there's some reason to make it visible again, this is easy enough to do.
--Chris
Posted: 24.03.2008, 03:01
by Chuft-Captain
Might be useful to leave it just so that the history of past fixes can still be seen.
CC
Re: Is there any reason to keep the CVS repository?
Posted: 27.03.2008, 13:44
by danielj
I didn?t understand.
CVN is the place to find Release Candidates(RC),or in other words,test versions that don?t need to be compiled.But what about the individual files and updates.Is there any CVN repository?Where is it?
Re: Is there any reason to keep the CVS repository?
Posted: 27.03.2008, 17:17
by t00fri
danielj wrote:I didn?t understand.
CVN is the place to find Release Candidates(RC),or in other words,test versions that don?t need to be compiled.But what about the individual files and updates.Is there any CVN repository?Where is it?
Daniel,
you composed a new repository name by contracting
CVS and SV
N ->
CVN, which (of course) does not exist.
Didn't we discuss many times already that the users who do not want to learn how to compile the code, will have to
wait until new official releases appear or some nice guys like cartrite do a compilation for you. Apart from that you can have a look in the Motherlode or at Celestia Matters.
The SVN is the new place where Celestia development takes place. But there you mostly don't find ready to use resources.
That's all there is.
F.
Re:
Posted: 27.03.2008, 17:38
by chris
Chuft-Captain wrote:Might be useful to leave it just so that the history of past fixes can still be seen.
CC
The entire history of revisions was preserved when I converted the CVS repository to SVN. Everything back to Feb 2001 is still there.
--Chris
Re: Is there any reason to keep the CVS repository?
Posted: 27.03.2008, 20:22
by danielj
But where is the svn directory?
Re: Is there any reason to keep the CVS repository?
Posted: 27.03.2008, 20:48
by selden
danielj wrote:But where is the svn directory?
Code: Select all
svn co https://celestia.svn.sourceforge.net/svnroot/celestia/trunk
Re: Is there any reason to keep the CVS repository?
Posted: 27.03.2008, 22:12
by cartrite
danielj wrote:But where is the svn directory?
Danielj,
Download Tortoise SVN from here.
http://tortoisesvn.net/downloadsAfter it is installed, when you right click somewhere, you should see svn checkout.
Click on that and a window appears.
Then add this line to "URL of repository:"
Code: Select all
https://celestia.svn.sourceforge.net/svnroot/celestia/trunkIt will then download the files. After, just right click on the celestia folder and choose svn update.
cartrite
Re: Is there any reason to keep the CVS repository?
Posted: 30.03.2008, 02:48
by danielj
There is a problem with this link...the page couldn?t be found!
Re: Is there any reason to keep the CVS repository?
Posted: 30.03.2008, 12:41
by selden
danielj wrote:There is a problem with this link...the page couldn?t be found!
Daniel,
It is not a URL for use with a Web browser. It is for use with Subversion.
Re: Is there any reason to keep the CVS repository?
Posted: 30.03.2008, 12:42
by ajtribick
Re: Is there any reason to keep the CVS repository?
Posted: 31.03.2008, 06:35
by BlindedByTheLight
I've been away for awhile but just happened to stumble onto this thread. The source code has been moved?
Does that mean I have to start all over with my Mac OS X monkey-button pushing way of compiling the source code? Prior, I used Terminal to download the source code then used Xcode to compile. Anyone know if I can do it basically the same way?
Steve
Re: Is there any reason to keep the CVS repository?
Posted: 31.03.2008, 10:40
by ElChristou
BlindedByTheLight wrote:I've been away for awhile but just happened to stumble onto this thread. The source code has been moved?
Does that mean I have to start all over with my Mac OS X monkey-button pushing way of compiling the source code? Prior, I used Terminal to download the source code then used Xcode to compile. Anyone know if I can do it basically the same way?
Re: Is there any reason to keep the CVS repository?
Posted: 01.04.2008, 06:38
by BlindedByTheLight
Thanks ElC. Am I correct to assume that's how one updates my code. But how do I get it down in the first place?
Thanks,
S
P.S. And is it me...or has this forum changed its appearance?
Re: Is there any reason to keep the CVS repository?
Posted: 01.04.2008, 11:15
by ElChristou
BlindedByTheLight wrote:Thanks ElC. Am I correct to assume that's how one updates my code. But how do I get it down in the first place?
Thanks,
S
P.S. And is it me...or has this forum changed its appearance?
It's you I think...
I don't even recall to have redownloaded the whole source... Dw, osX builders, any commands before updating?
Re: Is there any reason to keep the CVS repository?
Posted: 01.04.2008, 12:09
by selden
Blinded,
With the command line version of subversion, the initial setup and download is accomplished by creating and cd'ing to an appropriate directory, and then use this command to download the current development code for Celestia v1.6.0:
Code: Select all
svn checkout https://celestia.svn.sourceforge.net/svnroot/celestia/trunk
It's about 100MB.
Code: Select all
svn checkout https://celestia.svn.sourceforge.net/svnroot/celestia
Will download the sourcecode for all previous versions of Celestia, but that's more like 1GB.
Re: Is there any reason to keep the CVS repository?
Posted: 01.04.2008, 15:36
by symaski62
selden wrote:Blinded,
With the command line version of subversion, the initial setup and download is accomplished by creating and cd'ing to an appropriate directory, and then use this command to download the current development code for Celestia v1.6.0:
Code: Select all
svn checkout https://celestia.svn.sourceforge.net/svnroot/celestia/trunk
It's about 100MB.
Code: Select all
svn checkout https://celestia.svn.sourceforge.net/svnroot/celestia
Will download the sourcecode for all previous versions of Celestia, but that's more like 1GB.
ok +1 "trunk"
Re: Is there any reason to keep the CVS repository?
Posted: 06.04.2008, 03:05
by BlindedByTheLight
Thanks Selden,
I tried using Terminal (the unix command line GUI for OS X)...and got this:
MBP17-2:~ bud$ svn checkout
https://celestia.svn.sourceforge.net/sv ... stia/trunkError validating server certificate for 'https://celestia.svn.sourceforge.net:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Tue, 09 Oct 2007 22:15:07 GMT until Mon, 08 Dec 2008 23:15:07 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: fb:75:6c:40:58:ae:21:8c:63:dd:1b:7b:6a:7d:bb:8c:74:36:e7:8a
(R)eject, accept (t)emporarily or accept (p)ermanently?
I tried temporarily...and it worked. Is that right?
S
Re: Is there any reason to keep the CVS repository?
Posted: 06.04.2008, 11:57
by ElChristou
BlindedByTheLight wrote:I tried temporarily...and it worked. Is that right?
I suppose it will ask you again next time... If so try permanently to avoid the message in the future.