Hi,

I've written a draft version of a setup guide for compiling packages yourself. A reason for compiling yourself might be you want to develop your own spec files, or you want to verify builds for more security or every other reason of your choice.

My personal most appreciated reason for you having a build environment would be that you plan to contribute to the repository of spec-files and improve the number and / or quality of the provided software packages!.

You can read here and please remember to drop me a note with comments of any type:

https://sfe.opencsw.org/manual-setup-build-enviroment

Please note: Learning to write spec-files might take some time. Well, it does take long. Just compiling exisitng spec-files can sometime be a very easy thing, sometime it might be tricky.

But once you get used to the RPM spec files, it work well. RPM spec files are used for some Linux distros too...

Other projects this month:

* fail2ban - get the existing spec file fixed to have ipfilter work out of the box, add examples

I've setup a OmniOSce instance with fail2ban to protect SSH, postfix SASL and dovecot. I'll try to share examples

* SFEsamba410.spec - I'd write about a setup guide for an Active Directory Server on OmniOSce / Solaris 11.3 / 11.4 or OpenIndiana. The project is reaching the final stage, after that is finished I can start writing the setup guide. If you are interested, then let me know so I can send you a draft version.

* SFEsamba411.spec - the new 4.11 branch removes own crypto code and needs adjusted SFE patches. As well, changes to the cryto code should be tested very well, I don't want to risk broken kerberos or such.

* Note about Solaris 11.4 - Most of the exisiting packages are planned to be rebuilt in the complete GA version, in case they have older digits in the long form of package version numbers .

If you want to contribute to SFE, then you are welcome! Regardsless if you use OmniOSce, Solaris 11.3 or 11.4 or OpenIndiana Hipster. Contribution can be improving this blog page, this can be testing packages or even become a maintainer for spec-files!

Even putting a desired package into the wishlist is a welcome contribution!

Regards

Thomas