Code.google.com is closing I guess it's SF.Net that is best for SVN.

Hello,

Earlier today, Google announced we will be turning down Google Code Project Hosting. The service started in 2006 with the goal of providing a scalable and reliable way of hosting open source projects. Since that time, millions of people have contributed to open source projects hosted on the site.

But a lot has changed since 2006. In the past nine years, many other options for hosting open source projects have popped up, along with vibrant communities of developers. It’s time to recognize that Google Code’s mission to provide open source projects a home has been accomplished by others, such as GitHub and Bitbucket.

We will be shutting down Google Code over the coming months. Starting today, the site will no longer accept new projects, but will remain functionally unchanged until August 2015. After that, project data will be read-only. Early next year, the site will shut down, but project data will be available for download in an archive format.

As the owner of the following projects, you have several options for migrating your data.

basilisk-ii-for-amigaos
allegro5foramigaos

The simplest option would be to use the Google Code Exporter, a new tool that will allow you to export your projects directly to GitHub. Alternatively, we have documentation on how to migrate to other services — GitHub, Bitbucket, and SourceForge — manually.

For more information, please see the Google Open Source blog or contact google-code-shutdown@google.com.

-The Google Code team

@LiveForIt

Mplayer for AmigaOS4 is also hosted at code.google.com, it has to be moved some where.

@LiveForIt

The OS4 SDL port is too

Any one know if SGIT is usable or not?

@LiveForIt

You can checkout projects with it just fine
It's still in a pretty early development state, so not much else will be possible, but Sebastian is working on it

I think FryingPan sources are at Code.google.com too.

@all

What would it take to get a fully working git client? I quite like github's system, but it's not much use for AmigaOS projects unless we have a working git client.

Hans

@Hans

I guess someone has to start here :)

@orgin/Hans

Sebastian Bauer (simplemail) is already working on one

edit: Would OpenAmiga be a possibility for all those amiga google.code projects?

@orgin

Quote:
I'm pretty sure that at least one person already started there, but got stuck at some point. I'm wondering what those roadblocks are.

@Raziel

Quote:
I hadn't heard of that project. I hope that he can get that to a usable state.

Hans

@Hans

Quote:
I may be completely wrong but i remember someone telling me that a github client would need a complete rewrite (or written from scratch) due the use of permit()/forbid()

@Raziel

Only AmigaOS use permit()/forbid(), Linux don't use that.

My guess is that they are using fork().

Fork can split a program into more threads at any place in the code, and the threads can also exit at any place, fork() is kind of modern day Gosub, make the code hard to understand, and it make code unstructured, no clear start, nor end of etch thread.

Fork is often its used in combinations with networking, so that you can have different thread accepting incoming traffic, on different sockets, it can also be used to parallel uploads, so you can upload more than one file at the time.

In AmigaOS4.1 there is bit trick to getting socket sharing to work over many threads, so even if you rewrite the code, you can get problems getting it to work correct, because the bsdsocket library has to be opened by etch thread. In addition, there was one more issue with bsdsocket.library I do not remember.

@LiveForIt

You are absolutely right

fork() it was

@Raziel

Ah, so it was fork() that was the problem. Let's see how Sebastian goes with simplegit.

Hans

If you are considering version control you should consider Mercurial and www.bitbucket.org

I think it was BroadBlues who did the amiga client, so no reason to wait for git to get DVCS on Amiga

Steen

@Shadow

Mercurial/HG was a one-time port from Andy to close the gap of not having a github client et al

The port is outdated now, won't install/work under FE anymore and i won't repeat what Andy said about the port the last time i asked him

So don't consider mercurial an alternative or stop-gap solution right now

@Raziel

I am using Mercurial everyday at work and it is certainly not a stop gap solution :)

For amiga you are probably right, I have not used the port myself, as I mostly do cross compiling.

I think I will take a look at the port.

@Shadow

The mercurial port isn't that bad, it's the hg-git extension that is pants.

But it is old an old version 2.5 I think and they are up 3 .something now.

The reason it fails under FE is that python added the termios module and that triggers a bit of code that isn't supported. I have a work arround for that that makes a direct call to the console to get the info needed.

I'm maxed out time wise so if you want my source (the changes are fairly small) I'm happy to send you it.

Regardless of how good other revision control systems are, there is currently only one complete and reliable client for OS4 and that's Subversion (SVN). If you put the sources in an SVN repository at Sourceforge, you can always move the sources to another type of revision control system when a good Amiga client program becomes available without changing the project name or location.

@Xenic

Thanks.

Sourcefroge has provided some information about how to migrate SVN's.

http://sourceforge.net/blog/how-to-mi ... oogle-code-to-sourceforge