World: r3wp

Did you try the custome package source yet?

I'm beginning to wonder what is going to happen if we try to use 
git on many of the older systems...

Let me reformat the above in the hope of making it more readable:

1. edit /etc/apt/sources.list, add the following line:

  deb http://ppa.launchpad.net/git-core/ppa/ubuntulucid main

2. apt-get update
3. apt-get install git-core

And in step 1, replace the "lucid" with the name of the ubuntu version 
you are using.

(i.e. dapper, hardy, intrepid, jaunty)

Yes, that's what I did. Only part of that older package list is valid... 
the rest 404's.

Unfortunately, it is the binary-i386 that 404's

Run apt-get update twice, and see if it still 404's.

ok...

What Ubuntu version are you using?

This system is breezy_badger (5.10).  (I use older versions to prevent 
building unrunable releases.)

Well, that would have helped. Breezy is simply too old.

They don't have binaries built for breezy in that repository.

It should be possible to build it from source.  I need git on at 
least one primary build system here.

I can write a small REBOL script to sync the source over to the other 
build systems... which will probably never have the ability to run 
git.

I'm remembering now one of the reasons I wrote devbase (R3 chat)... 
to make this step easier.

Or just use rsync, if it's available on those systems.

git works fine on recent solaris, freebsd, openbsd. and even aix 
and hp/ux.

I'll need to see if rsync is on bsd and some of the others. Don't 
know.

If you're using a HP/UX from, say, 1990, you'll probably be out of 
luck, though.

I have all those systems, minus the word "recent".

I try to stay about 3-5 years behind "recent" in order to make the 
code work over the greatest range of systems.

Not a good strategy on some forward-lookin platforms, though.

It's funny how few operating systems are designed to just run software, 
not to become continuous IT management projects.

Well, forward-looking platforms either run prior code, or are totally 
new, so require some degree of time investment to get started on 
them.

Well, just as REBOL deprecates "disarm", other projects deprecate 
what they deem dangerous legacy.

REBOL uses so little of the OS libs, we could almost have our own 
libs to replace them.  Exceptions are the TCP stack and stdio/filesystem.

heh.. I thought Carl was going to say he was using Amiga System V 
unix

No, but I do have an Amiga here with 4.1. I should check if it's 
running git.

Steve said it is not.

ditto

(ssolie)

Let's get back to the issue of getting Git to run on Ubuntu Breezy 
:) ?

Ok. So much for distributed automated build, test, release.

We can start by concentrating on the "big three".

Let me see if I can find a curl-config that runs... then I can try 
the build again.

apt-get install libcurl3-gnutls-dev

(that contains curl-config)

Is there an apt-get option to ignore errors in deb urls?

You'll probably need to adapt your apt source, since breezy has been 
archived for a while.

Instead of 
  deb http://us.archive.ubuntu.com/ubuntu/breezy main restricted
use

  deb http://old-releases.ubuntu.com/ubuntu/breezy main restricted
(and change all other URLs accordingly.)

In other words, replace all *.ubuntu.com URLs by old-releases.ubuntu.com

Then run apt-get update, twice.

ok, that exists. progress!

those are the git build dependencies as marked in ubuntu packages:
https://gist.github.com/9cb86c37385fb66f9016

(all ubuntu package names)

compile goes a long way... blows out at http fetch.

try `make NO_CURL=1`

is git-http-fetch necessary?

Not really. Only if you want to access repositories via http:// or 
https://.You can live fine without that.