On Mon, 3 Mar 2014 09:28:20 +0100, nap <napar...@gmail.com> wrote: > I don't understand.
OK, I guess my question wasn't clear, giving full context may help: I want to package shinken modules since I need to install them without using shinken cli. For packaging software, one needs upstream releases (eg. mod-livestatus-2.0) with their tarballs available somewhere through a persitent URL (eg. http://shinken-monitoring/pub/modules/mod-livestatus-2.0.tar.gz). This tarball of one release shouldn't change over time, the checksum must stay constant. How could we proceed to download constant tarballs of the releases of shinken modules? -- Rémi Palancher http://rezib.org ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
