Welcome to CRUX bug tracking.
FS#1410 - pkgmk - add support for binary packages
Attached to Project:
CRUX
Opened by Fun (fun) - Monday, 01 May 2017, 16:25 GMT
Last edited by Fun (fun) - Sunday, 18 June 2017, 16:41 GMT
Opened by Fun (fun) - Monday, 01 May 2017, 16:25 GMT
Last edited by Fun (fun) - Sunday, 18 June 2017, 16:41 GMT
|
DetailsPKGMK_PACKAGE_CACHE_REGEX="(wxgtk|firefox)#"
PKGMK_PACKAGE_CACHE=(http://crux.ster.zone/packages/3.3/) The best practice for every port update is to rebuild the port (prt-get depinst) in a pristine container, with only core packages, and no sexy CFLAGS. Doing this, the maintainer has "the package", and it will be pity not to put it somewhere, for others to use it, especially when it will take 15min*10 to build it on a slow machine. From day one I've asked why do people leave CRUX. And I've asked for me, to know what to avoid. While I didn't get a clear answer, I've seen messages like: tired of building packages. Even these days, on the #crux channel. I've attached the patch 0002 a second time, with a fix to avoid downloading packages when "force build" option is used. Patch 0003 try all the extensions (gz, bz2, xz) regardless of PKGMK_COMPRESSION_MODE, and use a symlink if needed. Patch 0004 add signature support. |
This task depends upon
I've adapted the above patches to work when sourced from /etc/pkgmk.conf.
This is "binary package support for the masses".
PKGMK_MAKE_PACKAGE_SIGNATURE=yes
when doing:
prt-get update firefox --margs="-sk=... -pk=..."
and the masses will have signature support too.
After asking on #bash, it was a surprise to discover that in following two cases, the "set -e" behavior differ:
(set -e; false; true) || echo $?
(set -e; false; true); echo $?
In the first case, true is still executed.
The new variable (PKGMK_PACKAGE_MIRRORS) isn't documented nor initialized, but this shouldn't be a problem for someone interested.