Thread: [Shinken-devel] Permanent URL on modules tarballs
Status: Beta
Brought to you by:
naparuba
Menu
▾
▴
shinken-devel
|
From: Rémi P. <re...@re...> - 2014-02-27 16:18:10
|
Hi there, For distribution packaging, it's always better to have permanent URL to the upstream source tarball. I start looking for packaging shinken modules with livestatus as the first candidate. But unfortunately, I can't find URL to the released tarballs of this module on shinken.io website. Where can I find one? If there's none, is it possible for shinken.io maintainers to make modules' tarballs URL visible to users? Thanks, -- Rémi Palancher http://rezib.org |
|
From: nap <nap...@gm...> - 2014-02-27 19:42:49
|
On Thu, Feb 27, 2014 at 5:17 PM, Rémi Palancher <re...@re...> wrote: > Hi there, > > For distribution packaging, it's always better to have permanent URL to > the upstream source tarball. > > I start looking for packaging shinken modules with livestatus as the > first candidate. But unfortunately, I can't find URL to the released > tarballs of this module on shinken.io website. Where can I find one? If > there's none, is it possible for shinken.io maintainers to make modules' > tarballs URL visible to users? > > Thanks, > -- > Rémi Palancher > http://rezib.org > > Hi, Shinken.io is only done for the shinken cli, not for be the sources of tarballs :) You will find the sources of all default modules there: https://github.com/shinken-monitoring Happy packaging :) Jean |
|
From: Rémi P. <re...@re...> - 2014-02-28 08:29:01
|
On Thu, 27 Feb 2014 20:42:43 +0100, nap <nap...@gm...> wrote: > Shinken.io is only done for the shinken cli, not for be the sources > of > tarballs :) Fine. > You will find the sources of all default modules there: > https://github.com/shinken-monitoring OK but there is no release tags on some git repositories. For example with livestatus: https://github.com/shinken-monitoring/mod-livestatus/releases How could I know which commit to pick to build my package? -- Rémi Palancher http://rezib.org |
|
From: nap <nap...@gm...> - 2014-02-28 09:24:04
|
On Fri, Feb 28, 2014 at 9:28 AM, Rémi Palancher <re...@re...> wrote: > On Thu, 27 Feb 2014 20:42:43 +0100, nap <nap...@gm...> wrote: > > Shinken.io is only done for the shinken cli, not for be the sources > > of > > tarballs :) > > Fine. > > > You will find the sources of all default modules there: > > https://github.com/shinken-monitoring > > OK but there is no release tags on some git repositories. For example > with livestatus: > https://github.com/shinken-monitoring/mod-livestatus/releases > > How could I know which commit to pick to build my package? > > We can jsut tag the master, it doesn't changed since long, should be near the 1.4 version in fact. Jean |
|
From: Rémi P. <re...@re...> - 2014-02-28 13:25:34
|
On Fri, 28 Feb 2014 10:23:58 +0100, nap <nap...@gm...> wrote: > We can jsut tag the master, it doesn't changed since long, should be > near the 1.4 version in fact. Do you mean that module maintainers will do that systematically, as a general rule? -- Rémi Palancher http://rezib.org |
|
From: nap <nap...@gm...> - 2014-03-03 08:28:26
|
On Fri, Feb 28, 2014 at 2:25 PM, Rémi Palancher <re...@re...> wrote: > On Fri, 28 Feb 2014 10:23:58 +0100, nap <nap...@gm...> wrote: > > We can jsut tag the master, it doesn't changed since long, should be > > near the 1.4 version in fact. > > Do you mean that module maintainers will do that systematically, as a > general rule? > > I don't understand. Modules now live in their own repo with their own release cycle. Aside webui, lot of the enhancement were done in the core framework instead of the modules since the 1.4 version if it's what you ask. Jean |
|
From: Rémi P. <re...@re...> - 2014-03-03 11:49:08
|
On Mon, 3 Mar 2014 09:28:20 +0100, nap <nap...@gm...> 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 |
Thanks for helping keep SourceForge clean.
X