My package source tarball contains some "convenience copies of code". I have modified the package to use to the external package instead, so this code is now unneeded and unused. Unfortunately, my upsteam's upstream, (ie. the source my upstream copied from), also included some unsourced binaries (documentation in the form of .pdf), with this code. Except for the unsourced binaries, this code is properly licenced. I must remove these, creating a dfsg tarball. It has been suggested by a respected reviewer that while I am removing the unsourced binaries, I remove ALL of the "convenience copies of code". That way the unused code would not confuse anyone. I thought, that when creating a dfsg tarball, one should remove only the files with licensing problems. What is the proper procedure? Remove only the unsourced binaries, or all of the unused code? -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
Attachment:
signature.asc
Description: This is a digitally signed message part.