Hi,due to recent discussions I decided to discuss this in a separate thread to get it done :)
We've three options to distribute md5sums- create one big md5sum file for each release (kde 4.0.70, kde 4.0.71) we do --> kde_4_0_70.md5sum
- create a md5sum for every package (dbus-mingw-123456, dbus-msvc-123456, kdelibs-msvc-123456, ...) --> dbus-mingw-123456.md5sum
- create a md5sum for every file (dbus-mingw-12345-bin, dbus-mingw-12345-lib, dbus-mingw-12345-doc, dbus-mingw-12345-src) --> dbus-mingw-123456-bin.md5sum
I prefer the second one.The installer/emerge would then first fetch the md5sum for the package and then download the file. Later when the file needs to be fetched again we look for the md5sum and check if the file is correct. And only if this isn't the case we'll refetch it from the net.
I also read about signing the packages but have no idea how to do so. Comments? Christian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Kde-windows mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-windows
