Sure. The change which Max is suggesting only affects running the test
suite while fink is being bootstrapped, and also during the first time
the user upgrades to fink-0.18.0 (or whatever release this code becomes
part of). After that, the test suite will be run each time the user
installs fink.
Dear fink-devel,
I've added code which causes the fink test suite to be run every time you
bootstrap or inject fink. This required the introduction of three new
essential packages in the 10.2-gcc3.3 tree and earlier: file-spec-pm,
test-simple-pm, and test-harness-pm.
Please let me know if you en
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David R. Morrison wrote:
Thanks for the suggestion, Max, I'll look into modifying t/00compile to
make this work (although I'm a bit scared to touch that!).
personally I think that the whole purpouse of the test suit is defied if
we cannot or bet
I agree that making these packages essential is not a great solution.
In fact, if we make the test code conditional on the presence of the
Test:: stuff, then we can just add these packages to the bootstrap
when needed (like with storable-pm560).
Thanks for the suggestion, Max, I'll look into modif
P.S. If you are running on 10.2, you should install test-simple-pm by hand
before updating fink from CVS HEAD. The "essential" versions of the new
packages are present during the bootstrap, but haven't yet been added to
the unstable trees.
---
Am Donnerstag, 04.12.03 um 16:03 Uhr schrieb David R. Morrison:
P.S. If you are running on 10.2, you should install test-simple-pm by
hand
before updating fink from CVS HEAD. The "essential" versions of the
new
packages are present during the bootstrap, but haven't yet been added
to
the unstab
