Re: make php to multi packages

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

oskar%fessel.org@localhost writes:

> sorry for being late with additional questions…
> Anyone else seeing this?  And what can be done without resorting to „make update“?
>
> ——schnipp---
> ===> Building binary package for php83-8.3.16
> => Creating binary package /usr/pkgsrc/packages/All/php83-8.3.16.tgz
> ===> Replacing for php83-8.3.16
> *** Error code 1
>
> Stop.
> make[1]: stopped making "replace" in /usr/pkgsrc/lang/php83
> *** Error code 1

Two recommendations:

1) replace harder

1A) force delete

  pkg_delete -f php
  make package-install

  then pkg_rr again. check that all your php83-* have been rebuilt.
  This seems to have worked for me.  This is not about multiversion php
  so much as a renamed package.

  This is ugly/unsound because it loses the dependencies.   You can also
  after force-replace do 'pkg_admin set unsafe_depends=YES php83-*'.
  (Will set php itself, but basically extra replaces when they build are
  not a big deal.  FWIW I use ccache, too, so replacing a package just
  built, if it's in C/C++, is fast.)

1B) use OLDNAME

  make replace has a way to ask to replace a package of a different name.

  I think this might be 'make replace OLD_NAME=php'.   Read
  mk/pkgformat/pkg/replace.mk for details....

2) binary packages and pkgin

  In general, updating to a new branch and building can be trouble, and
  takes a long time (days, not minutes), so I basically don't want to do
  that on production machines, where production for me means difficulty
  if it is not working (mail server, etc.).

  Therefore I have build machines (mostly a bunch of domUs, but a
  physical RPI3) for multiple cpu/versions.  I do pkg_rolling-replace
  there and if it takes me a while to fix it that's ok.  Then I use
  pkgin.

  Whether this is coded right for pkgin SUPERSEDES, and whether that
  works right, is an interesting question, but figuring that out would
  be useful and fixing it would be useful too.