I wrote short article on 'life of binary packages'
(sorry in Japanese)
But that is not enough. My real life of binary packges is:
- prepare CHROOTED pbulk environment
- watch the stable date of pkgsrc
(and checkout that date)
cvs update -D yyyy-mm-dd
recent example is 2021-09-27
- create personal meta-package
The package name beginning with config- is important in this context
- run pbulk with /limited_list = config-set (etc)
recent example is:
local-mef/config-set
local-mef/config-R2021
local-mef/config-office
local-mef/emacs-desktop
local-mef/config-cad
local-mef/config-latex
pkgtools/pkgin
wm/fvwm3
- store the results somewhere
＠
install or update to new release:
- copy (presumably by wget) binary to local filesystem
You need explicit version name, wget won't allow wildcard.
check by following. (Supposing to have (old) pkgin is installed))
pkgin search pkgin
- pkgin
- pkg_install
- sudo
- pkg_delete -ff '*'
- su
- pkg_add sudo (and exit from su)
- sudo pkg_add pkgin
- set repositories.conf to one of binary repository listed above
- sudo pkgin install config-set
＠
todays error (problem):
some package should not be and are not included
Those should not be in personal binary packgage.