--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hubert Feyrer <hubert@feyrer.de> wrote:
>=20
> It would be nice to have files with checksums of binary packages=20
> available, esp. after bulk builds. Possible options to implement that=20
> would be either
>=20
> a) at "make package" time, where $PKGDIR/../../$checksumfile could be=20
> updated. An old checksum of the same filename should be removed. Maybe=20
> this checksum processing should only if PKG_DEVELOPER or BATCH (=3D=3D bu=
lk=20
> build) is set. Or
>=20
> b) after bulk builds, for all packages in one go. Disadvantage here is
> that it would re-calculate checksums of pkgs that didn't change, which ma=
y=20
> waste some cycles (e.g. if you have your packages on a slow NFS server :).
>=20
> Needed checksums are what is available for NetBSD releases too: BSDSUM,=
=20
> CKSUM, MD5, SYSVSUM.
>=20
> Is anyone interested in working on this?

I have this on my (mental) todo list.

I was thinking about doing it as part of the 'upload' script (ie more of
(b) than (a)), with a knob to pgp sign the final checksum file (which
would introduce/require interaction).

But I haven't looked at this at all yet, so if people think it would be
better to do this as part of the actual 'make package' target, I
wouldn't be opposed to that, either.

-Jan

--=20
Tradition is the illusion of permanence. -- Woody Allen

--6TrnltStXW4iwmi0
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFB8oHVfFtkr68iakwRAriGAJ4uJ9Z8FbQDcxSys950VSwgVNE2ogCfaJ0K
JYnXLGU8NpaAghyBN1n+FG8=
=FXtS
-----END PGP SIGNATURE-----

--6TrnltStXW4iwmi0--