Re: Built-Using usage question

Lukas Schwaighofer writes: > Ok, I expected as much. Any suggestions on where to put that? > /usr/share/doc/syslinux-efi/copyright seems like the obvious place (and > is mandated by policy §12.5) but if I understand the machine readable > format correctly, it doesn't

Re: Built-Using usage question

Hi, On Sat, 30 Dec 2017 19:42:01 -0800 Russ Allbery wrote: > I don't think you need to change anything about Built-Using. That > seems like exactly the sort of reason anticipated by DFSG > compliance. The clarification in Policy is because the previous > wording would have

Re: Built-Using usage question

Paul Wise writes: > Personally, I feel this change to policy is a mistake. Alternative proposals that achieve the goal of not adding Built-Using fields to the entire archive are welcome. -- Russ Allbery (r...@debian.org)

Re: Built-Using usage question

Lukas Schwaighofer writes: > The syslinux-efi binary package contains parts of the gnu-efi package > due to static linking. I believe that, independent of the license > question, in order to satisfy DFSG §2 (“The program must include source > code, […]”) I need to keep

Re: Built-Using usage question

On Sat, Dec 30, 2017 at 10:49 PM, Lukas Schwaighofer wrote: > I read the update in policy 4.1.3 and I'm not sure how to handle the > change / clarification of the Built-Using control field for the > syslinux package (which I maintain in the debian-cd team). I suggest you ask this question on the

Built-Using usage question

Hi mentors, I read the update in policy 4.1.3 and I'm not sure how to handle the change / clarification of the Built-Using control field for the syslinux package (which I maintain in the debian-cd team). I have two questions: The syslinux-efi binary package contains parts of the gnu-efi package