Am 27.12.21 um 21:19 schrieb Friedrich Kink via oi-dev:
Hi all,
Hi Friedrich,
welcome to OpenIndiana. I am happy that you will provide help for some interesting areas where we miss specialists.
reading silently for a couple of years this mailing list I decided now to contribute to the community my extensions I made over the years to my system (at least I'd like to try ;-)). The main purpose of my system is to act as mail server supporting all modern security features like DANE, SPF, DKIM, DMARC etc (which works btw for couple of years already, basically I started with opensolaris). That's why I'll focus on those packages. Of course I've some questions after starting this endeavor. Especially when trying to build Spamassassin which requires a lot of additional Perl modules. While start building these modules it turned out that the provided 64bit Perl version 5.24 is pretty outdated. So I built the current stable version 5.34 based on the existing 5.24 setup. Worked like a charm ;-). Now first question: Is there a reason/dependency for not upgrading to a newer version? Next question: Some Perl modules have odd version like 1.04 which makes publishing a package impossible because of the padding zero in the number after the dot. What is the reason for bailing out on a padding zero (just a
I recommend to clone our main repository: OpenIndiana/oi-userland (https://github.com/OpenIndiana/oi-userland). Within this you'll find a folder named "doc" that contains important information, eg. reserved_uids_and_gids.md, which may answer your question regarding user and group ids (hint: the file needs an update if you add something). Start reading on our documentation server, eg. "Building with oi-userland" (https://docs.openindiana.org/dev/userland/). Regarding odd version numbers like 1.04 in your example. Alas we are restricted to what FMRI gave us and the version numbers are just a part of the package's FMRI. While we are stuck on this there are some helping definitions possible, eg. by additionally use IPS_COMPONENT_VERSION (this is the one that ends in the FMRI and is automatically set by COMPONENT_VERSION if not explicitly set to another value) and HUMAN_VERSION, which can additionally be used to add the "real" version information for a package. See for an example what actual components/sysutils/sudo does to provide the HUMAN_VERSION (hint: you'll need to have a definition in the Makefile and also a reference in the manifest). It is always a good idea to look for existing solutions for a problem you encounter. Typically it has already been solved by other packages.
question for me and my understanding ;-))? Also, some packages will require a new user and/or group. Are uids/gids managed centrally or can I just choose some numbers <100 not used to my best knowledge? How to store test results (I haven't found the trick where the results get stored in the test directory while comparing existing packages with mine). And finally when I think I'm ready to release my package would this list be the place to ask for integration? thanks a lot for all the work already, Fritz
Regards, Andreas _______________________________________________ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
