Re: Bob woes

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

* On 2026-09-02 at 17:28 BST, Rhialto wrote:

> - tell Bob it should just let "make package" put the file where it
>  wants, and not meddle with it afterwards. I don't know if this is
>  currently possible, but it seems the only reasonable solution.

Possibly, but I'd need to think this through carefully.  Currently bob 
does exactly the same as pbulk in this regard - running stage-install 
and then stage-package-create to generate the binary package, then 
perform pkg_add/pkg_delete to test the install, and then finally copy 
the binary package manually to $PACKAGES.

The initial goal was to replicate pbulk's behaviour for the vast 
majority of the actual pkgsrc side of things to get things running, and 
then maybe look at any incremental improvements.

pbulk did previously use the "package" target which would avoid the 
manual copy, but switched to separate steps.

> (I realise it's also possible that Bob doesn't copy the packages to
> /pkg_comp but instead there is some weird chroot escape bug that doesn't
> show up when I try things manually, but that seems less likely for now)

Yeh it's not this, just that bob (running outside) is performing the 
copy to what it has determined to be the PACKAGES directory.

One of the reasons for pbulk's $sync_package was to support multiple 
build hosts without NFS or similar, i.e. copy the generated binary 
package around to all build hosts before completing the build.  As 
distributed builds is a specific non-goal of bob then it's much more 
likely that I can move back to 'make package' and then this should all 
just work for you.

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