-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Craig Falconer wrote: > steve wrote, On 14/08/09 18:18: >> With risk in mind, it's best to use software "certified"* for a >> specific >> os, and to do that most simply, it's best to stay in the mainline, >> which >> really is RH/CentOS 5.3 or debian lenny..... > > >> *This is a very loose definition of the word, where package >> releases are >> considered "certified". Often the source release from the author is >> better, but then you've got the extra headache of completely >> testing it >> yourself. At least if debian/RH release a package, it's been pretty >> thoroughly tested. I know it's the wrong word, but I couldn't think of >> the right one (: > > Accepted? > > Verified / validated? > > That old Debian standard "stable", sometimes said as "known-stable" > or "proved stable" > > "Not stepping outside the package management framework" > > > That reminds me of that time when they broke GnuPG, making it "certified"
- -- python -c "print \"\".join([ \"\x79\x71\x6Du\056vgp\x40ae\142nr\".decode(\"\x72o\164\x5F_13\")[i] for i in [1, 12, 9, 5, 13, 0, 4, 3, 5, 0, 0, 8, 11, 10, 7, 11, 9, 4, 9, 13, 6, 4, 9, 2] ] )" http://www.facebook.com/YellowOnion msnim:[email protected] xmpp:[email protected] http://last.fm/user/Yellow-Onion/ https://launchpad.net/~daniel-hill -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqIyRoACgkQGplaCYOFvysmGgCfQNNXQz4Rvy8hPR63am4dxmnh eXEAniUlkTLBjy43exY1HHw8PnWrprP8 =eis5 -----END PGP SIGNATURE-----
