using bob to build for several hosts, python versions again

[Greg Troxel <gdt%lexort.com@localhost>]

I'm switching a domU package builder over to bob, from a more
manual/pkg_rr approach, to see how that goes (mostly well).

First, I had to redo the sandbox setup, because everything's on nfs from
the dom0 zfs, and I had to deal with NFS permisions a bit -- but that's
not a bob problem and not really that hard.

I have scripts that ssh to N hosts and run "pkgin sk", and then union
that and diff it with the output from the builder.  I have aimed to have
the builder have everything installed.  With build builds, I don't need
it installed, but instead it should be on the list of packages to build.

However, bob uses PKGPATH, not PKGNAME, and that's an easy switch -- use
"pkgin export" instead.

There are then two problems:

  - carry the information about which python version is installed (as
    pkgin sk would have shown) into a build control file

  - only build the versions that are needed, because they are the
    one that's installed

I think "build the default version (typically) when there is a python
dependency of a non-py-versioned package" (e.g. bup) is ok.

As an example I have

  py313-certbot

installed.  That leads to

  security/py-certbot

which leads to building certbot for every pyversion, and all of the
dependencies for every pyversion.

It seems there should be some mechanism for this.  I tried putting
security/py313-certbot in the pkgpaths file, but unsurprisingly that did
not go well.


I think the root of the trouble is that PKGPATH and PKGNAME are both
partial, and we don't have a way to specify both at once, someting like

  security/py-certbot PYTHON_VERSION_REQD=313


I realize I can set something to default to only 313, but I might have
some package where I want 314 for it.



Am I missing something, or is it just not possible to deal with this
reasonably right now?


The good news is that this is my big problem -- everything is working
well otherwise.