Ansgar Burchardt wrote: > Thomas Goirand <tho...@goirand.fr> writes: > > Both problems do not comply with the Debian Policy for main: > >> - The source.zip provided, once extracted, contain a folder "Installer >> Source" which contain a file called "Installer Script.nsi" to be used >> with the "Null soft installer" from nullsoft.com. So the sources of the >> installer are really there, this is all what's needed to ship! Did you >> believe something else should be shipped? > > Policy 2.2.1: > In addition, the packages in main must not require a package outside of > main for compilation or execution (thus, the package must not declare a > "Depends", "Recommends", or "Build-Depends" relationship on a non-main > package)
Which is not the case here. Where exactly did you see that any of the binary (that are built for Debian) that are built need something outside main? It's absolutely allowed to have some (open source) source code that can't be built in Debian in the source package, if they are not used in the built process or later on by the package, and if nothing depends on the binary that is by the way not packaged as binary for Debian. If what I'm saying is not right, please show me the part of the policy that forbids what I did (and not the above, which doesn't match my case). >> - Still in the "Installer Source" you find these libraries. These are >> built from the OpenSSL windows port. Do you as well believe I should >> ship the full of the OpenSSL windows port in it? > > Policy 2.1 (DFSG): > Source Code > The program must include source code, and must allow distribution in > source code as well as compiled form. Which is the case. I am allowing you to distribute both! I'm not in the violation of the policy here, as everything that is used in the package has source code. Even for that windows binary, there is the source code, and you are allowed to do anything with it (it's LGPL). I am NOT shipping the nullsoft installer here... > The program seems not to be included in any binary package anyway, so > maybe it could just be removed from the tarball used by Debian? Why do you want to remove it? It makes absolutely no sense. I am just giving access to the windows binary in the source package. I didn't see anything in the policy that forbids that, especially if they are not packaged in the .debs that are built. You'll have to make a better case here, otherwise it will stay the way it is, as I have no proof of policy violation. Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
