Il 04/11/2012 20:14, Jakub Wilk ha scritto: > * Giulio Paci <giuliop...@gmail.com>, 2012-10-27, 18:28: >>>> I finally decided to repackage the tarball with files generated by more >>>> recent versions of swig. >>>> I used an interface file downloaded from >>>> https://github.com/shogo82148/TinySVM/. >>> The binding should be regenerated at build time. But... are they currently >>> used at all? If not, it might be simpler just to strip them out completely. >> I do not know any user of the bindings, but I would prefer to keep at least >> their sources in the package (I have to repackage the tarball anyway and the >> bindings sources >> do not introduce a large overhead), if it is not a problem to leave the >> source there and not compiling them. > > If the idea is to leave out all the generated files, but keep the SWIG > interface file, then yes, it should be fine.
Fine, so I will re-package it leaving out the automatically generated files. The idea is to remove problematic files and add these files (6270 bytes) from https://github.com/shogo82148/TinySVM/: java/test.java java/Makefile.in python/setup.py python/README swig/TinySVM.i swig/Makefile Is this ok? >>> In any case, please provide a get-orig-source target. >> I have no experience with this target. > > Very well! That means you'll learn something new. ;) > >> I read the description on this page >> (http://www.debian.org/doc/debian-policy/ch-source.html), but I did not >> understood what I am supposed to do. >> As far as I understood, this target should provide a way to get the sources >> for the patched upstream tarball. >> Anyway the description reports that the target should: >> 1) download the original source file; >> 2) recreate the patched source; >> 3) tar the patched source. >> >> It is possible to implement these steps, but I need some software to do that >> (e.g., something to retrieve files from upstream and from >> https://github.com/shogo82148/TinySVM/ and the same version of swig that I >> used to recreate the bindings file). >> How should I handle these additional dependencies? > > There's no standardized way to declare which packages are needed for > get-orig-source. This is not a problem in practice, as this target is run > only by humans, who are > usually smart enough to figure out what's needed. :) As long as you use tools > that a typical developer is more or less familiar with, you should be fine. I can do everything using uscan, tar, sed and wget, so I think this is not a problem. During the process I need to create a temporary directory. Should I delete it at the end of get-orig-source? Should I delete it in clean? How should I call the final package? Bests, Giulio. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50972151.5090...@gmail.com
