[ANNOUNCE] qgit4 aka qgit ported to Windows

I have setup, (thanks Pasky) the repository

     git://repo.or.cz/qgit4.git


With an experimental version of qgit, called qgit4.

Features are the same of qgit-1.5.4  release but has been ported under
Qt4.2 libraries from Qt3, this means that could be compiled and run as
a Windows native application.

Qt4.2 is available as GPL for non commercial purposes also for Windows platform.

So what you need is:

1) Qt4.2 already packaged with MinGW for windows
(http://www.trolltech.com/developer/downloads/qt/windows)

2) Cygwin with git files

3) qgit sources from the above public repository

4) Compile using qmake that will build proper Makefile for you

    - qmake qgit.pro
    - make
    - (make install is supported only under Linux at the moment)

5) Open a terminal with cmd.exe, add Qt and MinGW bin dirs to PATH
(already added if you run the ready to use Qt command prompt menu that
comes with Qt installation), add cygwin bin directory to PATH,
something like:

               set PATH=%PATH%;C:\cygwin\bin\directory


6) Start qgit.exe

7) Have fun

NOTE NOTE: DO NOT RUN from a cygwin terminal, as I said qgit it's a
*native* Windows application when compiled with Qt4.2 so you don't
need that.

Well, I have tried to run from a cygwin terminal and it works almost
the same (of course you need to add Qt and MinGW bin dirs to path as
always) but it's much slower and has some little issues with the
different paths conventions.

NOTE: This is 'alpha' quality software, not all features are already
working so be prepared to few surprises.

Marco

P.S: Of course the same sources work (better) also under Linux.

On Tuesday 09 January 2007 22:14, Marco Costalba wrote:

I have setup, (thanks Pasky) the repository

     git://repo.or.cz/qgit4.git


With an experimental version of qgit, called qgit4.

Nice.

Why not as branch in the original qgit repository?
You are losing all your history this way.

Josef

On 1/9/07, Josef Weidendorfer [off-list ref] wrote:

On Tuesday 09 January 2007 22:14, Marco Costalba wrote:

quoted

I have setup, (thanks Pasky) the repository

     git://repo.or.cz/qgit4.git


With an experimental version of qgit, called qgit4.

Nice.

Why not as branch in the original qgit repository?
You are losing all your history this way.

Well, Qt4 it's completely different from Qt3, porting it's a nice way
to say rewrite. So moving patches between the two branches it's very
difficult already now and it will be impossible in a near future not
because of development forking, but because of API. This means two
different and *not mergeable* branches.

Being not mergeable they lose the main motivation to be in the same
repository IMHO. Also I would like to continue to support and improve
the stable and proven Qt3 version on kernel.org that is and will be
the main version.

Perhaps when qgit4 will be stable enough I will ask to move to
kernel.org but now, for easier development I asked to Pasky, that
kindly accepted, to host this repo.

Marco

On Tue, Jan 09, 2007 at 11:30:34PM +0100, Marco Costalba wrote:

Being not mergeable they lose the main motivation to be in the same
repository IMHO.

Well, this also means you lose the history trail of you project.  Just
suppose one day you'll face a piece of your code which you don't
understand any more (face it, we all have that strange "did *I* write
that ?" feeling some day ;).  Being able to hunt it down is nice - and
grafting the qt3-based repo will only be useful it you know precisely
where to put the graft...

Best regards,
-- 
Yann.

On 1/10/07, Marco Costalba [off-list ref] wrote:

6) Start qgit.exe
7) Have fun

Great!

How much does qgit4 depend on using commandline git? IOWs, how far
from not needing cygwin+git, and shipping a git+qgit compiled against
the MinGW that QT4 has?

cheers,


martin

Hi,

On Thu, 11 Jan 2007, Martin Langhoff wrote:

On 1/10/07, Marco Costalba [off-list ref] wrote:

quoted

6) Start qgit.exe
7) Have fun

Great!

How much does qgit4 depend on using commandline git? IOWs, how far

quoted

from not needing cygwin+git, and shipping a git+qgit compiled against

the MinGW that QT4 has?

I do not understand what QT4 has to do with git compiling against MinGW. 
It is a totally different kind of kettle.

I outlined the difficulties with MinGW already, see 
e.g.http://article.gmane.org/gmane.comp.version-control.git/14047

Ciao,
Dscho

Martin Langhoff wrote:

How much does qgit4 depend on using commandline git? IOWs, how far
from not needing cygwin+git, and shipping a git+qgit compiled against
the MinGW that QT4 has?

FWIW, I'm slowly working on a MinGW port of git, based on Dscho's
initial work.

Currently, the tool set passes about 60-70% of the tests.

This works: The tools that you commonly need to work on a local repo,
except merges ([*]): commit, rebase, reset, log, diff and their
plumbing.

This does not work: pull, fetch, clone; mostly due to fork()
difficulties in their plumbing (fetch-pack, send-pack, etc.)

[*] because shell scripts like merge-one-file can't be invoked from an
exe like merge-index, yet. Fortunately this looks like the easiest part
to solve.

-- Hannes

Hi,

On Thu, 11 Jan 2007, Johannes Sixt wrote:

This works: The tools that you commonly need to work on a local repo,
except merges ([*]): commit, rebase, reset, log, diff and their
plumbing.

[...]

[*] because shell scripts like merge-one-file can't be invoked from an 
exe like merge-index, yet. Fortunately this looks like the easiest part 
to solve.

Exactly. Just build-in merge-one-file. This has the further benefit that 
we (finally) can use the inbuilt xdl_merge() without a fork()!

And then, we'll get Alex' merge under 1 minute.

Ciao,
Dscho

On 1/11/07, Martin Langhoff [off-list ref] wrote:

On 1/10/07, Marco Costalba [off-list ref] wrote:

quoted

6) Start qgit.exe
7) Have fun

Great!

How much does qgit4 depend on using commandline git? IOWs, how far
from not needing cygwin+git, and shipping a git+qgit compiled against
the MinGW that QT4 has?

qgit4 does not depends on  commandline git environment at all. You can
start qgit4 also without a git installation, also without a cygwin
installation either. Of course it's not useful in that cases.

I had no time to fix some rogh edges regarding launching qgit4 with
proper paths set. What I plan to do this week end is to find an 'easy
to use recipe' to start qgit4 from cmd.exe, from desktop icon and also
from cygwin shell.

I need to experiment a little bit with this but I would like to add
internal automatic recognizing of environment at least for cmd.exe vs
cygwin shell launching case so to let user have a nice experience in
both cases.

  Marco

Marco Costalba wrote:

On 1/11/07, Martin Langhoff [off-list ref] wrote:

quoted

On 1/10/07, Marco Costalba [off-list ref] wrote:

quoted

6) Start qgit.exe
7) Have fun

Great!

How much does qgit4 depend on using commandline git? IOWs, how far
from not needing cygwin+git, and shipping a git+qgit compiled against
the MinGW that QT4 has?

qgit4 does not depends on  commandline git environment at all. You can
start qgit4 also without a git installation, also without a cygwin
installation either. Of course it's not useful in that cases.

Huh? Does qgit4 have all the git plumbing built in?

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

On 1/11/07, Andreas Ericsson [off-list ref] wrote:

Marco Costalba wrote:

quoted

On 1/11/07, Martin Langhoff [off-list ref] wrote:

quoted

On 1/10/07, Marco Costalba [off-list ref] wrote:

quoted

6) Start qgit.exe
7) Have fun

Great!

How much does qgit4 depend on using commandline git? IOWs, how far
from not needing cygwin+git, and shipping a git+qgit compiled against
the MinGW that QT4 has?

qgit4 does not depends on  commandline git environment at all. You can
start qgit4 also without a git installation, also without a cygwin
installation either. Of course it's not useful in that cases.

Huh? Does qgit4 have all the git plumbing built in?

No. It's absolutely not useful without git (but compiles and runs
anyway). What I mean is that beign a native windows application it
does not need cygwin. The latter is needed only by git.

On 1/11/07, Johannes Schindelin [off-list ref] wrote:

Hi,

On Thu, 11 Jan 2007, Johannes Sixt wrote:

quoted

This works: The tools that you commonly need to work on a local repo,
except merges ([*]): commit, rebase, reset, log, diff and their
plumbing.

[...]

[*] because shell scripts like merge-one-file can't be invoked from an
exe like merge-index, yet. Fortunately this looks like the easiest part
to solve.

From an exe you could run:

     cmd.exe /c  <script with arguments>

Of course the problem is that the content of the script should be
understandable by cmd.exe windows interpreter.

Marco Costalba wrote:

quoted

On Thu, 11 Jan 2007, Johannes Sixt wrote:

quoted

[*] because shell scripts like merge-one-file can't be invoked from an
exe like merge-index, yet. Fortunately this looks like the easiest part
to solve.

quoted

From an exe you could run:

     cmd.exe /c  <script with arguments>

Of course the problem is that the content of the script should be
understandable by cmd.exe windows interpreter.

We are talking about git's own scripts, which are (ba)sh and perl.

The route I'm going is to do the path lookup manually (if necessary),
then look at the first few bytes of the file for the interpreter, then
something like

 spawnvp(<interpreter-w/o-path>, <full-path-of-script plus args>)

-- Hannes