Kandarp,<div><br></div><div>I think your question is on packaging, where we are using a different concurrency version control system, other than git. I think the steps should remain the same. Community members, please confirm if there is a difference?</div>
<div><br></div><div>Copying Mike on this memo, who can answer your questions related to exelearning code structure.</div><div><br></div><div>Regards,</div><div><br></div><div>Manu</div><div><br></div><div><br><br><div class="gmail_quote">
On Wed, Aug 4, 2010 at 10:39 PM, Kandarp Kaushik <span dir="ltr"><<a href="mailto:kandarp@seeta.in">kandarp@seeta.in</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><div>Hello,</div><div><br></div><div>I was trying to package eXe ( <a href="http://exelearning.org/wiki" target="_blank">http://exelearning.org/wiki</a> ) for debian.</div><div><br></div><div>eXe uses subversion for as the concurrency revision control system. More information at:</div>
<div><a href="http://exelearning.org/wiki/SourceControl" target="_blank">http://exelearning.org/wiki/SourceControl</a></div><div><br></div><div>It will help if someone could provide some pointers on how eXe should be packaged.</div>
<div>
<br></div><div>Regards,</div><div>Kandarp.</div>
</blockquote></div><br></div>