Hi Bastien, On Thu, Jan 23, 2014 at 07:31:43PM +0100, Bastien ROUCARIES wrote: > ressource and not compiled inside doxygen.
>From my point of view it does not matter whether the doxygen package ships jquery inside a binary or in a separate file. Both are contained in the package and both are compiled (albeit differently). What you describe is not a worthwhile goal to me. > My goal is to move the data from c file compiles to run time. Thus 1. 2. 3 > or your readme.jquerry are not used for debian. If you intend to work on aspect 1. (embedding of jquery sources in the doxygen source package) then surely the first step would be *packaging* the missing libraries. Can you point me to the work you have done in that area? I also do not see any aspects of you addressing embedding 2. or 3. (minified jquery in doxygen source package). At no point do you add code that touches the build system. Your initial patch does not address any of your claimed goals! > And so on means I have done for one file but I will do for all file > including png if needed. As I have pointed out in my previous mail, I do not see moving the resources from one place to another as a worthwhile goal. > My goal is to automatically generate a data package. After I will use > compatibilty layer of jquerry in order to replace link in generated package. I have already investigated this option. When I asked Doxygen upstream about API stability of the bundled jquery libraries Dimitri explicitly denied any kind of forwards- or backwards-compatibility. That means that any documentation package depending on a doxygen-data package will need a versioned dependency. When a new version of doxygen gets uploaded, all reverse build-dependencies therefore need to be rebuilt. Unfortunately for us, most of them are Architecture:all and we currently only do Architecture:any binNMUs. While I agree that this would ultimately be the best outcome, it is not currently possible. If you intend to further this goal, please work on Architecture:all autobuilding. Unless you add substantial information to this bug report, I am inclined to close it. As is, this bug report is in no way actionable. Helmut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
