<br><br><div class="gmail_quote">On Mon, Aug 16, 2010 at 00:55, Eli Barzilay <span dir="ltr"><<a href="mailto:eli@barzilay.org">eli@barzilay.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On Aug 15, Laurent wrote:<br> </div><div class="im">> > The problem is that both .deb files and .rmp files are designed so<br> > > that you package the source with instructions on how to compile<br> > > them into binaries. But our build process produces the binary<br> > > packages and therefore going from there to .deb/.rpm files is very<br> > > awkward.<br> ><br> > I thought it was possible to make .deb files from binaries only.<br> > But maybe I'm mistaken.<br> <br> </div>I think that it's possible too, but what I remember is that basically<br> every step of the way feels wrong -- things like using a compiled<br> directory as "the source" etc. </blockquote><div><br>After some searching, maybe EPM (<a href="http://www.epmhome.org">www.epmhome.org</a>) is a good solution.<br>It seems to be a nice, simple, Unix multi-platform package manager <br> from binaries.<br>It was very easy (noob here) to create a .deb file from a Racket medium<br>size project.<br>It can also create .dmg, .rpm, and many (all?) other Unix formats + <br>a portable .tar.gz one, from a /single/ configuration file.<br> It deals with subpackages and dependencies.<br>It can have a GUI with fltk.<br>(if during install it says some libs are missing, get the -devel/-dev ones, <br>it should work).<br></div></div><br><br>Hope this can help someone,<br> Laurent<br>