[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#567719: ITP: haskell-sdl -- Haskell SDL binding for GHC



Hola Miriam.

Em Dom, 2010-01-31 às 05:55 +0100, Miriam Ruiz escreveu: 
> 2010/1/31 Erik de Castro Lopo <mle+hs@mega-nerd.com>:
(...) 
> > The majority of the debian haskell pacakges are currently in darcs, so
> > it would be my advice to only use git if you already have these packages
> > in git.
> 
> I don't have a clue on how to use darcs.
(...) 
> I'm not sure I have enough spare
> time right now to learn darcs, to be honest, that's why I suggested
> git. Any suggestions?

I just like to add that, in my opinion, darcs is very similar to git,
but more simple and intuitive, because it has a very good user
interface.  If you already know git, I don't think you'll have to spend
much time to learn darcs.  Most of what you'll need is described in
http://wiki.debian.org/Haskell/CollabMaint/DarcsBasic .

For a start, just run the darcs command and you'll get a list of the
possible commands:

$ darcs

In a basic usage, all you'll need is add, record (git commit), tag, pull
and push.  If you're going to work with other packages, you'll also need
get (git clone).  There're some other commands which are very useful,
such as revert (git reset --hard HEAD), whatsnew (git diff),
amend-record (git commit --amend), unrecord (git reset --soft),
obliterate (git reset --hard).

Notice you don't need to study each command parameter, because darcs is
interactive, and will ask you the questions needed.

As most of the packages are in darcs right now, it's much easier to do
maintenance in them if they're all in the same directory in the server,
using the same VCS software.  And there's a "feature" of the group
that's not available to git currently, which is PET:
http://pkg-haskell.alioth.debian.org/cgi-bin/pet.cgi

Despite that, if you really prefer to use git, there're some other
packages in git, and this is also an option currently.

Greetings.
(...)
-- 
marcot
http://marcot.iaaeee.org/



Reply to: