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 not
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 gui
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
progre
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
comp
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