Re: [oi-dev] Providing icinga2 package

2017-12-06 Thread Aurélien Larcher
Hello!


> that's the way I'm trying now, after lots of RTFM ;) First test build is
> running now. What's the reason you never published 2.7.2?
>

The main reason is lacking of testing.
We make sure that packages pushed to the main repository are in a good
shape.


>
> > I wrote some additional notes to build a maintainer's guide (work in
> > progress), you can also have a look at it:
> Very helpful, thank you! Lots of information, especially for a newbie
> like me.
>

I can create a wiki account for you if you want to amend some of the
content.
Juste let me know.


> I'm on freenode, too; when I'm getting stuck, I'll ping you all on
> #oi-dev :)
>

Alright :) Good luck!

Kind regards

Aurelien


>
> Cheers,
>   Marianne
>
> --
> https://www.unixe.de/
> https://www.urban-exploring.eu/
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Providing icinga2 package

2017-12-06 Thread Marianne Spiller
Hi Aurelien,

> You can base your work on the component I prepared for testing the
> compilation of 2.7.2:

that's the way I'm trying now, after lots of RTFM ;) First test build is
running now. What's the reason you never published 2.7.2?

> I wrote some additional notes to build a maintainer's guide (work in
> progress), you can also have a look at it:
Very helpful, thank you! Lots of information, especially for a newbie
like me.

I'm on freenode, too; when I'm getting stuck, I'll ping you all on
#oi-dev :)

Cheers,
  Marianne

-- 
https://www.unixe.de/
https://www.urban-exploring.eu/


smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Providing icinga2 package

2017-11-29 Thread Aurélien Larcher
Dear Marianne,
welcome to the mailing list!

You can base your work on the component I prepared for testing the
compilation of 2.7.2:

https://github.com/alarcher/oi-userland/commit/7fcbef3038180699d344dad4a1970d2c2d0c4263

I wrote some additional notes to build a maintainer's guide (work in
progress), you can also have a look at it:

https://wiki.openindiana.org/oi/3.+Common+Tasks

Kind regards

Aurelien

On Wed, Nov 29, 2017 at 2:27 PM, Till Wegmüller 
wrote:

> Hi Marianne
>
> To get started grab yourself a copy of
> https://github.com/OpenIndiana/oi-userland
>
> The Best Way is to clone this repo and setup a fork in your own github
> profile. You can then make a remote and push to your profile.
>
> Make a Feature branch for every componetn you want to package. A
> component is the software itself and not all packages built from that
> component. In your case it should be icinga and maybe if another
> dependecy is needed one more component. The reason for that is that we
> want seperate pull-request per component so it is more easily to check
> what has been done.
>
> The readme gives you a good starting point for building components that
> already exist.
>
> A compoent itself consists of a manifest and a makefile which controls
> the build
>
> The makefile is documented at:
> https://wiki.openindiana.org/oi/oi-userland+Makefile+targets+and+variables
>
> I think the best component to orient yourself when building icinga will
> be zabbix. Also have a look at the pull requests if any of them help you
> with your work.
>
> If you have further questions don't hesitate to write to the ML or drop
> by in #oi-dev on freenode
>
> Hope this helps
> Greetings
> Till
> On 29.11.2017 13:22, Marianne Spiller wrote:
> > Hi there,
> >
> > I successfully compiled icinga2-2.8.0 on OpenIndiana Hipster 2017.10,
> > we're running it on several machines without any problems. So the
> > community asked me to publish it as a package for the official repo -
> > I'm willing to do so, but I'll need some assistance from more
> > experienced users (I tried RTFM like that:
> > https://wiki.openindiana.org/oi/Building+with+oi-userland, but it seems
> > outdated).
> >
> > So any help would be appreciated: I'd like to provide icinga2 as a
> > package, what's best practice?
> >
> > Cheers,
> >   Marianne
> >
> >
> >
> > ___
> > oi-dev mailing list
> > oi-dev@openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Providing icinga2 package

2017-11-29 Thread Till Wegmüller
Hi Marianne

To get started grab yourself a copy of
https://github.com/OpenIndiana/oi-userland

The Best Way is to clone this repo and setup a fork in your own github
profile. You can then make a remote and push to your profile.

Make a Feature branch for every componetn you want to package. A
component is the software itself and not all packages built from that
component. In your case it should be icinga and maybe if another
dependecy is needed one more component. The reason for that is that we
want seperate pull-request per component so it is more easily to check
what has been done.

The readme gives you a good starting point for building components that
already exist.

A compoent itself consists of a manifest and a makefile which controls
the build

The makefile is documented at:
https://wiki.openindiana.org/oi/oi-userland+Makefile+targets+and+variables

I think the best component to orient yourself when building icinga will
be zabbix. Also have a look at the pull requests if any of them help you
with your work.

If you have further questions don't hesitate to write to the ML or drop
by in #oi-dev on freenode

Hope this helps
Greetings
Till
On 29.11.2017 13:22, Marianne Spiller wrote:
> Hi there,
> 
> I successfully compiled icinga2-2.8.0 on OpenIndiana Hipster 2017.10,
> we're running it on several machines without any problems. So the
> community asked me to publish it as a package for the official repo -
> I'm willing to do so, but I'll need some assistance from more
> experienced users (I tried RTFM like that:
> https://wiki.openindiana.org/oi/Building+with+oi-userland, but it seems
> outdated).
> 
> So any help would be appreciated: I'd like to provide icinga2 as a
> package, what's best practice?
> 
> Cheers,
>   Marianne
> 
> 
> 
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
> 

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


[oi-dev] Providing icinga2 package

2017-11-29 Thread Marianne Spiller
Hi there,

I successfully compiled icinga2-2.8.0 on OpenIndiana Hipster 2017.10,
we're running it on several machines without any problems. So the
community asked me to publish it as a package for the official repo -
I'm willing to do so, but I'll need some assistance from more
experienced users (I tried RTFM like that:
https://wiki.openindiana.org/oi/Building+with+oi-userland, but it seems
outdated).

So any help would be appreciated: I'd like to provide icinga2 as a
package, what's best practice?

Cheers,
  Marianne

-- 
https://www.unixe.de/
https://www.urban-exploring.eu/


smime.p7s
Description: S/MIME cryptographic signature
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev