debian package

[Mildred Ki'Lya]

Le Thu 04/09/2008 __ 16:08 picca __ __crit:
> Hello
> 
> One thing before developping with git.
> 
> what about using a part of the git.git branch organization to develop
> lisaac. They send all there patch on the mailing list for review then
> a person is in charge of applying them to the official repository.

I don't think that anyone should push their changes to the official
repository. Instead they should modify the compiler in their own
branch, and from time to time ask with Benoit to merge.

And everyone is free to push their branch either in gna (they have ssh
access but no easy web interface as far as I can see) or somewhere
else. For example http://gitorious.org

> the risk with git is to have a very complicate history if you do not
> have someone in charge of this. and becarefull the history can be
> modify 'a posteriory'.

How is that possible ?
Isn't the history hashed using SHA1 cryptographic algorithm. If you
manage to change the history (for example using git rebase) it should
also change the identifiers of the changesets.

> We need a debian branch to let the debian directory evolve
> independently of the other branches.
> So the debian directory must not be part of next or master.
> 
> If we want to use git-buildpackage to build debian package from the
> aliot git repository of the compiler. we must create an upstream

I have no idea how debian packages works, for me it is far too
complicated (creating a package should be something straightforward).
But I don't see the problem of keeping the debian directory with the
compiler. If we had no debian developer in the team it would be another
story, but that's not the case.

Mildred

-- 
Mildred Ki'Lya
______________________________ ____________________________________________________________ ______________________________
___ Jabber, GoogleTalk: <mildred at jabber.fr>
___ Site: <http://ki.lya.online.fr>              GPG ID: 9A7D 2E2B
___ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B