--s/l3CgOIzMHHjg/5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Hubert Feyrer writes:
>=20
> It would be nice to have files with checksums of binary packages=20
> available, esp. after bulk builds.

What do you intend to use them for?

> 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.

Just an idea for plan b): You could have one checksum file for each package=
.=20
You then compare the timestamps to see which of them needs to be updated.=
=20
Finally, you can merge them into one big file, if you like.

--=20
Lasse Kliemann
      private homepage: http://plastictree.net
   NO software patents: http://swpat.ffii.org
do NOT use M$ products: http://plastictree.net/articles/noms

--s/l3CgOIzMHHjg/5
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFB8moO1gObwed86AkRAlFaAKCbifNuQ4aOdt1vpIgLft2QtCdCTACgwJcP
Xjqr9M7juQdA3zNNc5NHWas=
=RkR/
-----END PGP SIGNATURE-----

--s/l3CgOIzMHHjg/5--