Re: Intentionally smaller pbulk builds

[Jonathan Perkin <jperkin%pkgsrc.org@localhost>]

* On 2024-12-26 at 08:21 GMT, Thomas Klausner wrote:

> On Thu, Dec 26, 2024 at 04:06:53AM +0000, John Klos wrote:
> > If I wanted to limit a pbulk run to, say, just use php83 and not php81 and
> > php82 (leaving out php56 and php74), and likewise wanted to just use
> > python312 and not python39, 310, 311, and 313 (leaving out python27), and
> > lua, and ruby, et cetera, how might I do that?
>
> Set
> PYTHON_VERSION_DEFAULT=         312
> PYTHON_VERSIONS_INCOMPATIBLE+=  310 311 313
> PHP_VERSION_DEFAULT=            83
> PHP_VERSIONS_INCOMPATIBLE+=     56 74 81 82
> in your /etc/mk.conf.

What I do in my limited builds (as these hacks will really only work in 
limited builds), is e.g. set

  RUBY_VERSION_REQD=	${RUBY_VERSION_DEFAULT}

in mk.conf.

https://github.com/TritonDataCenter/pkgbuild/blob/master/include/pkgoptions/trunk.mk#L113-L119

> Depending on what you include in your bulk build, this might
> completely break its scan phase, if the bulk build includes a package
> that doesn't build with Python 3.12 or PHP 8.3. In that case, you'll
> have to check bulklog/meta/presolve for the failing package &
> PHP/Python version, and allow that PHP/Python version, or remove the
> package from your bulk build.

Yeh, trying to do this stuff for a full build will likely result in at 
least a week of playing whack-a-mole, not including time taken to re-run 
the scan.

--
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com