Is there any reason to keep the CVS repository?
Is there any reason to keep the CVS repository?
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?
-
- Site Admin
- Posts: 4211
- Joined: 28.01.2002
- With us: 22 years 9 months
- Location: Seattle, Washington, USA
Re: Is there any reason to keep the CVS repository?
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
- Chuft-Captain
- Posts: 1779
- Joined: 18.12.2005
- With us: 18 years 11 months
Might be useful to leave it just so that the history of past fixes can still be seen.
CC
CC
"Is a planetary surface the right place for an expanding technological civilization?"
-- Gerard K. O'Neill (1969)
CATALOG SYNTAX HIGHLIGHTING TOOLS LAGRANGE POINTS
-- Gerard K. O'Neill (1969)
CATALOG SYNTAX HIGHLIGHTING TOOLS LAGRANGE POINTS
Re: Is there any reason to keep the CVS repository?
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?
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?
- t00fri
- Developer
- Posts: 8772
- Joined: 29.03.2002
- Age: 22
- With us: 22 years 7 months
- Location: Hamburg, Germany
Re: Is there any reason to keep the CVS repository?
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 SVN -> 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.
-
- Site Admin
- Posts: 4211
- Joined: 28.01.2002
- With us: 22 years 9 months
- Location: Seattle, Washington, USA
Re:
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?
But where is the svn directory?
Re: Is there any reason to keep the CVS repository?
danielj wrote:But where is the svn directory?
Code: Select all
svn co https://celestia.svn.sourceforge.net/svnroot/celestia/trunk
Selden
- cartrite
- Posts: 1978
- Joined: 15.09.2005
- With us: 19 years 2 months
- Location: Pocono Mountains, Pennsylvania, USA Greate Grandfother from Irshava, Zakarpattia Oblast Ukraine
Re: Is there any reason to keep the CVS repository?
Danielj,danielj wrote:But where is the svn directory?
Download Tortoise SVN from here. http://tortoisesvn.net/downloads
After 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/trunk
It will then download the files. After, just right click on the celestia folder and choose svn update.
cartrite
VivoBook_ASUSLaptop X712JA_S712JA Intel(R) UHD Graphics 8gb ram. Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz, 1190 Mhz, 4 Core(s), 8 Logical Processor(s) 8 GB ram. Running on Windows 11 and OpenSuse 15.4
Re: Is there any reason to keep the CVS repository?
There is a problem with this link...the page couldn?t be found!
Re: Is there any reason to keep the CVS repository?
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.
Selden
Re: Is there any reason to keep the CVS repository?
If you want to browse the repository, go to http://celestia.svn.sourceforge.net/vie ... tia/trunk/
-
- Posts: 485
- Joined: 19.03.2005
- With us: 19 years 8 months
- Location: Los Angeles, CA
Re: Is there any reason to keep the CVS repository?
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
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
Steven Binder, Mac OS X 10.4.10
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 9 months
Re: Is there any reason to keep the CVS repository?
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?
Code: Select all
cd celestia
svn update
-
- Posts: 485
- Joined: 19.03.2005
- With us: 19 years 8 months
- Location: Los Angeles, CA
Re: Is there any reason to keep the CVS repository?
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?
Thanks,
S
P.S. And is it me...or has this forum changed its appearance?
Steven Binder, Mac OS X 10.4.10
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 9 months
Re: Is there any reason to keep the CVS repository?
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?
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:
It's about 100MB.
Will download the sourcecode for all previous versions of Celestia, but that's more like 1GB.
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.
Selden
Re: Is there any reason to keep the CVS repository?
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"
windows 10 directX 12 version
celestia 1.7.0 64 bits
with a general handicap of 80% and it makes much d' efforts for the community and s' expimer, thank you d' to be understanding.
celestia 1.7.0 64 bits
with a general handicap of 80% and it makes much d' efforts for the community and s' expimer, thank you d' to be understanding.
-
- Posts: 485
- Joined: 19.03.2005
- With us: 19 years 8 months
- Location: Los Angeles, CA
Re: Is there any reason to keep the CVS repository?
Thanks Selden,
I tried using Terminal (the unix command line GUI for OS X)...and got this:
I tried temporarily...and it worked. Is that right?
S
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/trunk
Error 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
Steven Binder, Mac OS X 10.4.10
-
- Developer
- Posts: 3776
- Joined: 04.02.2005
- With us: 19 years 9 months
Re: Is there any reason to keep the CVS repository?
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.