-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -=| Marc 'HE' Brockschmidt, 7.12.2006 18:49 |=- > Daniel Baumann <[EMAIL PROTECTED]> writes: >> ...but using a patch management system is strongly recommended from the >> q&a point of view. > > Assuming you meant QA here: No, it's not. If there would be only one > patch system, you would be right. But between no patch system, dpatch, > cdbs-simplepatchsys, quilt, dbs and home-brewn patch systems, half of > the QA work becomes figuring out how to apply the friggin patch for the > actual problem. > > It's more comfortable for normal package maintainers, though: Moving > changes to new upstream versions is reduced to cp -r $old/debian/ > $new/debian, apply errors can easily be seperated and it's easy to > forward stuff to upstream.
Marc, Where is the "proper" place for documenting the patch system used? README.Debian-source? By "proper" I mean where does QA team look for such information? How can we make QA's job easier, while still benefit from using a patch system? dam - -- Damyan Ivanov Modular Software Systems [EMAIL PROTECTED] phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFeEtTHqjlqpcl9jsRAjqSAJ9GEhwQGJNiMqmuWsVkOR2R07jAlACgsCPb /XgUQJCa1tnRfdaYPptmTQo= =VbVa -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]