Hi Tim,
READMEs along Pkgfiles are often ignored as well, so writing them might feel like a useless task, it might be better to make this more clear and explain the severity in the handbook.
I think README files are valuable, it was completely my inattentiveness that I did not enable runscripts option and directly run `prt-get depinst` without having a look into the `prt-get info` first to discover hints about READMEs and pre-/postinstall scripts. I think some lazyness I was getting used to from other package management system fell on my feet here. Nevertheless, I also think it would help to emphasize or warn about the fact in the handbook. Because, yes, indeed it was my first reference but I somehow overlooked the importance of some "details".
Well, it has it's own shortcomings. You can't say anywhere e.g. to build libreoffice with qt support and without gtk3, it will always build gtk3, and optionally enable qt support when you have qt5 installed, or other scenarios.
Hm, I do not know about libreoffice but could this not be solved by publishing two packages, a libreoffice-gtk3 and a libreoffice-qt5, each with specific build configurations? Or otherway around, is this really a CRUX issue or could this be fixed by a flexible build configuration which the libreoffice maintainers or developers should provide?
Few further tipps:
Many thanks for these! I am sure to make use of them following my future CRUX journey. —Martin