-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I disagree. Of course locally made checksums are not as safe as are
ones you get from the "vendors". but in the end, if their download
packages can be hacked and replaced by wormed packages, so can their
websites listing the MD5 checksums.
The "fink checksums" is a good tip, I didn't know about this.
Until someone adds "fink validate-all" etc. try my little finkutil
script:
/sw/fink/dists/experimental/carstenklapp/finkutil
:) Carsten
On Thursday, December 19, 2002, at 10:08 am, Max Horn wrote:
The next step would be run modi
At 6:45 Uhr -0500 19.12.2002, Kyle Moffett wrote:
On Wednesday, Dec 18, 2002, at 18:29 US/Eastern, Patrick Näf wrote:
I only thought to add ***new*** MD5 sums where they are missing.
Something along the lines of
find /sw/fink/10.2 -name *.info -exec fgrep -Hic source-md5 {} \; | grep :0$
I wou
On Wednesday, Dec 18, 2002, at 18:29 US/Eastern, Patrick Näf wrote:
I only thought to add ***new*** MD5 sums where they are missing.
Something along the lines of
find /sw/fink/10.2 -name *.info -exec fgrep -Hic source-md5 {} \; |
grep :0$
I would group the work by maintainer and, when I have
Before starting work I would make a final selfupdate-cvs and then put
aside the whole 10.2 tree. I would then add the fields to the .info
files, make a ball from the files for every maintainer and... do
what? Send it to them personally? Put it on the package submission
tracker?
This would be
On Monday, December 16, 2002, at 07:19 PM, Patrick Näf wrote:
Before starting work I would make a final selfupdate-cvs and then put
aside the whole 10.2 tree. I would then add the fields to the .info
files, make a ball from the files for every maintainer and... do what?
Send it to them perso
As part of my redemption for the sin of making negative comments on the
list :-) I would like to offer the following penance:
Quite a number of .info files don't have a Homepage or Source-MD5
field. If you people think that it would be worthwile I would make an
effort to provide the necessary i
