World: r3wp

Rebol is not the only language where file extension issues come up, 
but they're trying to take the sort of Apple philosophy of "we'll 
figure it out" as opposed to there being a web of settings.  It's 
just not high on their priority list to "sense" whether a file is 
Rebol or not.

But long term that's what they want, to sniff and guess instead of 
offer settings.  The GitHub people are very pragmatic, and opinionated, 
and (in my experience) quick and efficient.

The new default lookup extension for IMPORT is .reb, so maybe we 
can use that, or .r2 or .r3 for version-specific code.

I saw the .reb thing.  They would probably do that.  They've already 
given Rebol .r2, .r3, and .rebol ... tekkub and I seem to have a 
little bit of a rapport now so I could probably ask him to do .reb 
too

But still, why not .rebol ?

But you have to remember that R is really established, so it will 
be hard to take .r away from them in Github.

(-> "Source Control")

They were talking about recognizing the rebol header, that's what 
they want to do, they just don't have the priority.

I imagine that if RT said "hey we'd like to be your customers and 
pay you for a closed source hosting account of capacity X" then for 
some X they'd accept adding that sensor to the system as a priority.

Without that, they tend to their paying clients priorities first, 
I think.

Good point :)

You could add it to gitorious trivially, or run your own gitorious 
installation which favors .r for Rebol, but outsourcing things like 
this seems to me like it's worth every penny... esp when it's free.

Fork, _please_ move this discussion to "Source control".

Had the chance to read Git for Computer Scientists.

Any system that has a "rebase" cannot be all bad. ;)

rebase rocks :)

Checking for git on local ubuntu.

nope. not found

up until 10.04 the package is called "git-core"

for anything before 9.04 (jaunty), the packaged git-core is rather 
old, so you're probably better off installing from source.

yes, I was concluding that same thing.

git does not make

Strolling down a dangerous road...

Why should git be dependent on curl-config ?

must be what he uses for ssh.

you'll need:
libz-dev
libcurl4-gnutls-dev
libexpat1-dev

and probably also:

asciidoc, xmlto, docbook-xsl, subversion, libsvn-perl (or libsvn-core-perl), 
unzip, tcl85., gettext, cvs, cvsps, libdb-sqlite3-perl

(those should all be valid package names for ubuntu)

I just wonder - if SVN worked for RebGUI, would not it be sufficient 
for R3 too?

The versioned interdependencies of Linux systems are enough to blow 
your mind.

It didn't really work for rebgui ...

another (possibly simpler) option for recent git on ubuntu is to 
use third-party packages. just add 
deb http://ppa.launchpad.net/git-core/ppa/ubuntulucid main

to /etc/apt/sources.list, replacing "lucid" with the name or your 
distro. then do an `apt-get update` and `apt-get install git-core`

Everyone had their own forks which were not merged back in

Andreas, ok, will try that instead.

First, let me see if I can grab a working AltME for this linux box... 
so I don't need to keep looking back at a different screen ;)

AtlME installed.
Syncing this world.

Sure a lot easier installing AltME on Linux than most other apps. 
:)

Hopefully if people fork the hostkit we can now follow them using 
github

Ok, finally sync'd.

BTW, for AltME, created an R3 divider for the user list.

So, failed to obtain git binary or build git from source.

God is here !

No, just a humble scrappy coder.

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.