I agree with the Xavier, for the moment the compiler and editor should be enough for packages and after when we have stable <br>libraries like the opengl one we can think about other packages.<br>We could have one packages with the content of the compiler.git and several packages on for each editor mode.<br>
<br clear="all">M. Farzad Sehat<br><a href="mailto:farzad.sehat@gmail.com">farzad.sehat@gmail.com</a><br>
<br><br><div class="gmail_quote">2009/11/14 Xavier Oswald <span dir="ltr"><<a href="mailto:xoswald@gmail.com">xoswald@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On 11:10 Sat 14 Nov , PICCA Frédéric-Emmanuel wrote:<br>
> Hello<br>
><br>
> > Well,<br>
><br>
> > The fact is that we have a gentoo and debian branch since we have tools in the<br>
> > debian and gentoo project that understand the git structure and will then use<br>
> > the right branch.<br>
><br>
> > Before removing/moving anything we have to take a decision with Frederic about<br>
> > how we will work with debian.<br>
><br>
> > For gentoo, I think we can remove it since it's only one small file.<br>
><br>
> > So Frederic, what I suggest is keeping the debian branch and add a debian branch<br>
> > in the new editors.git and libraries.git so we will be able to build packages<br>
> > respectively for:<br>
> > * The compiler:<br>
> > - lisaac<br>
> > - lisaac-common<br>
> > - lisaac-doc (shorter)<br>
> > * Editors:<br>
> > - lisaac-vim-mode<br>
> > - lisaac-kate-mode<br>
> > - lisaac-emacs-mode<br>
> > - lisaac-EDITOR-mode ...<br>
> > * Libraries:<br>
> > - libbase-lisaac<br>
> > - libopengl-lisaac<br>
> > - libLIBRARY-lisaac ...<br>
><br>
> Ok so what you are discribing are the debian pakages names.<br>
> Maybe the best things to do is to have independant repository for the<br>
> packaging. No interaction with the upstreazm developpement.<br>
> No risk to make a mistake on the central repository.<br>
><br>
> So what I propose is<br>
><br>
> pkg-lisaac.git repository<br>
> pkg-lisaac-editors.git repository<br>
> pkg-lisaac-libs.git repository<br>
><br>
> the alioth way :)<br>
><br>
> then we importe directly on the standard git-buildpackage branch hierarchy<br>
> the official .tar.gz for each tree upstream repository.<br>
><br>
> lets call them:<br>
> lisaac.tar.gz<br>
> lisaac-editors.tar.gz<br>
> lisaac-libs.tar.gz<br>
><br>
> what do you think about this.<br>
<br>
</div></div>When we do a release, in the lisaac-X.tar.gz, you will have, compiler,<br>
documentation, editors support, external libraries (opengl etc..)<br>
<br>
I think keeping a debian branch in each git we want things to debian is easier<br>
and more flexible. I suggest a the beginning to have one in compiler.git and<br>
editors.git.<br>
<br>
Then we can release libraries independantly when a library is ready (opengl,<br>
sqlite, etc...).<br>
<br>
The fact is that the final lisaac-X.tar.gz tarball contains to much things and<br>
it's quite big to each time upload it to debian (about 15M) due to PDF<br>
ducumentation etc..<br>
<br>
Greetings,<br>
<font color="#888888">--<br>
,''`.| ====== Xavier Oswald ====== | mail: <a href="mailto:xoswald@debian.org">xoswald@debian.org</a> |<br>
: :' :| Engineer at CALDERA GRAPHICS | <a href="http://www.caldera.eu" target="_blank">http://www.caldera.eu</a> |<br>
`. `' | GNU/LINUX Debian Developer | <a href="http://debian.org" target="_blank">http://debian.org</a> |<br>
`- | Isaac Project Developer | <a href="http://isaacproject.u-strasbg.fr" target="_blank">http://isaacproject.u-strasbg.fr</a> |<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Lisaac-devel mailing list<br>
<a href="mailto:Lisaac-devel@lists.alioth.debian.org">Lisaac-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel" target="_blank">http://lists.alioth.debian.org/mailman/listinfo/lisaac-devel</a><br>
</div></div></blockquote></div><br>