Thanks for the insights and the gracious offer of building a binary for me.
I am willing to try "bootstrap your own 2021Qx release
yourself and build the necessary intermediate packages"
first though, as I'm always into learning something new.
However, most of my spare time is already taken by a number of projects, so... I could use some help on that route.
I have been looking around and trying something here and there,
but to me the pkgsrc documentation I found so far - whether it is
the official docs or your Joyent blogs and stuff - are either
extensive, fragmented or really outdated.
Is there any sort of "quick start guide" out there on building a package somewhat quickly, specifically for Illumos/OmniOSce?
I get that you build on SmartOS, but that's a different beast. I am very reluctant to go that road first, only because I missed a Nextcloud package. I mean... wow.
Regarding the alternative option that you point out in your final
paragraph: you write as if it is easy-peasy, but I hardly
understand what you're writing. Let alone where to begin.
Maybe you showing me how to build Nextcloud 21 myself will
consume way too much time from both of us anyway; I can't see how
much effort is needed either way. So, please advise.
* On 2021-11-30 at 12:04 GMT, Andries Annema wrote:
Is it somehow possible to "bootstrap" an older quarterly pkgsrc release from
I'm running some OmniOSce servers with the pkgsrc-repo bootstrapped onto it,
according to the instructions here:
I know how to do something like that with older 20xxQx-releases as available
but for some reason, no 2021Qx-tarballs are available there; 2020Q4 is the last
one, from then onwards only "trunk"-balls remain, but these don't give me what
I stopped producing quarterly releases as they just weren't all that useful, the vast majority of people either use a Q4 LTS release or follow trunk.
It's unfortunate that Nextcloud has such a restrictive upgrade procedure, but yeh there's no reason why you couldn't bootstrap your own 2021Qx release yourself and build the necessary intermediate packages, then just follow trunk to keep updated.
Alternatively you could set up a trunk pkgbuild instance, use git to revert the pkgsrc tree back to the version of www/php-nextcloud that you need, and then build it. Sometimes there will be complications with this method depending on how many strict dependencies have changed, but it may be simpler. If you run into issues with this just let me know and I can probably build it myself and send you the binary package.