-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: developers-reference Severity: wishlist
Hi, I'd like to see a section within the developer's reference for best practices dealing with upstream tarballs. In particular it would be helpful to have something quotable about: * when (not) to touch the upstream tarball * why the upstream signature does matter (or not) * when to repack the tarball and how to rename it successively (e.g. think of +ds1/+debian1 or +dfsg1 naming conventions) * How to deal with repacked tarballs (README.source files, get-orig-source targets) - -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJONuGHAAoJEMcrUe6dgPNtDvIQAM1wvVvRNPBN3dhKxZums4X4 tNYM/K4ak95xEOV5FkhsNN939Ap5tmtuuZeO5zOXEg6ymbKKqxAGPqhetPZgwg2j H329sOHkSaRC+776xw53B4EhcmUshMSGecg9D8Rb0DhcdiIz3exLtfxF2okrzr5Q JKbNMKX8xwbGCbce5TGHV81fynqDks6e1n77BnhWPMSLP8nWmIWhwppH+MMTLsPM bCmEi+7aGgvPFo6pfGMnfWNCs9HY4FpQIVSOShXPzQ0XB/pd5N20lRKQdXx4YwbT pdALOc4eDXXuvkDef944cl/t6Yd8ofPbhMekcGsK8syOawpPWoAIDx/g57ZjvY2R RoCsVQSiXWF3MWlti2DVSLjwD2ru9yoxlF67Ufblh6IhJCJ8ea2HQqZ1R4+BmtYx weC42Izl0FusqhJ5b8E5wPh1XlseW6RG3IkbLbl5ImmXD5k+a7eIqS4UvH9Igk1d 1TVXzD3nKvJe4c2+sbdEz8Mq0/jQ5Kjj8RdcZXxP18WTdYlIK6iSw/rpcDDzw6dS j+VrrmNgY+gQxcei6af71mQTyCjhwo77I0QL131Cj+isbPoi4teR5qGIMX28tcCI S1UvpHO/TBj9zrnsi6bu0jw9O5RkTnimYNtfqlmE8LAMYJ1mHPo9AqaSaKuB1CFf tXgUc4wIPFkQBh4X3SDd =b8Nk -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
