| |
LOGAN
Account closed
Registered: Aug 2003
Posts: 71 |
Source Control for C64 projects
An old dream of mine is having many coders on the C64 use SVN and having their code open source. And then coders could come together and join on projects.
Many coders still doing everything like 20 years ago alone, would it not be cool to have more open projects?
And it would also be cool to have more projects release their source code. (Many don't dare to release because of spagetti code I guess, hehe)
So who of you would think having a sourceforge like thing for c64 code projects would be cool?
(Maybe c64.org could have an SVN server for source projects... |
|
| |
Radiant
Registered: Sep 2004
Posts: 639 |
I would suggest using git instead of SVN, because it's simply better in almost every way. That said, there's nothing I know of that prevents C64 projects from being hosted on f.e. SourceForge. |
| |
LOGAN
Account closed
Registered: Aug 2003
Posts: 71 |
I don't know GIT.... and 99% of all projects use SVN. With tortoise its as easy as using windows..
Sourceforge is not perfect choice.. Projects need reviewing and I don't see many C64 coders join projects on sourceforge... Rather have something more aimed at c64 freaks :D |
| |
Martin Piper
Registered: Nov 2007
Posts: 722 |
Working on my own stuff at home I use Perforce. It has per-commit change history, like svn, but I find the tools for analysing differences in revisions to be more mature and hence easier to use in Perforce. Even working on my own I use revision control, it is a must for any project longer than half an hour. :)
Right now, all of my C64 code tends to end up on codebase64. |
| |
Conjuror
Registered: Aug 2004
Posts: 168 |
I use subversion for all my work, including c64 stuff. I have it installed as part of my $20 per month hosting.
Great just to have everything backed up offsite.
And I certainly back the idea of an "open" repository for c64 projects, including cross platform tools. |
| |
cadaver
Registered: Feb 2002
Posts: 1160 |
I do use private SVN for C64 stuff.
I guess a public repository would fit some projects, like tools, which can always be updated with more fixes, features etc.
But I don't know how many would like for example their unfinished upcoming C64 game be totally public.
|
| |
Radiant
Registered: Sep 2004
Posts: 639 |
SVN is rather horrible when it comes to merging branches etc., and that is something you will want to do sooner or later if you're collaborating with others. Add to that all the connectivity issues you can get when working with a centralized repository. There is really no reason not to use GIT. |
| |
LOGAN
Account closed
Registered: Aug 2003
Posts: 71 |
For many years the standard was CVS but then most open source projects switched to SVN. So the choice for SVN is not random, but because it's perhaps the most used one in the Open Souce world.
I kinda used CVS in the beginning and ported the whole history to SVN at some time using some hard to understand scripting, hehe. It worked out in the end though.
I can imagine some projects wanting to be a bit more private, but in the end a central point with open source C64 stuff could keep things alive for everyone to improve, learn from or expand on.
But sites like Google code and sourceforge any c64 project there will be flooded by other projects. Thats why I would wish for a C64 related version of a site like that. c64forge? hehe.
Crossing fingers... |
| |
Act-Otl
Registered: Feb 2008
Posts: 9 |
I use subversion for all my professional and hobby projects, however git is tempting, certainly if you have a project on which a lot of people collaborate.
Source control is one thing, but what I miss in the C64 world are libraries that we can reuse. Most will have collected a lot of code snippets they cut-copy-paste/link into their own projects.
For my own C64 projects I have created a small framework I can reuse. The only 'drawback' is that I mostly do my work in C (cc65) with some assembly sprayed onto areas that need to be fast. |
| |
Radiant
Registered: Sep 2004
Posts: 639 |
The same can be done for a number of typical demo routines with ca65 if you take time and care to write generalized code. Krill's loader is a fine example. |
