Thomas Goirand <z...@debian.org> writes: > On 11/14/2014 06:30 AM, Martin Geisler wrote: >> That is, I think Horizon developers will use these tools to produce a >> release -- a tarball -- and that tarball will be something you unpack >> on your webserver and then you're done. I base this on what I've seen >> in the project I've been working. The release tarball you download >> here don't mention npm, bower, or any of the other tools: >> >> https://github.com/zerovm/swift-browser/releases >> >> The tools were used to produce the tarball and were used to test it, >> but they're not part of the released product. Somewhat similar to how >> GCC isn't included in the tarball if you download a pre-compiled >> binary. > > When doing packages, I don't even use the tarball, but a git clone, > which itself produces an orig.tar.xz file. I do that to allow more > flexibility and to be able to do "upstream" code change easily.
Description: PGP signature
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev