On 2018-01-16 16:47+0100, Sébastien Villemot wrote: > On Tue, Jan 16, 2018 at 04:32:02PM +0100, Félix Sipma wrote: >> On 2018-01-16 12:46+0100, Sébastien Villemot wrote: > >>> Indeed you’re right. The zotero-web-library.js stuff is included in the >>> official Zotero client distribution. So lots of work ahead, I'm not sure >>> I'm up >>> to the task. I think I am going to orphan the package. >> >> I have to admit it did not motivate me either to see such a big work to do... >> Maybe an acceptable possibility would be to put the js libs in the package >> and >> move it in contrib? > > I'm not sure to understand your reasoning. > > Do you mean that the libraries would be downloaded at build time? This has > been > discussed on debian-devel@ recently, and it is clearly not acceptable, even > for > contrib. > > Or do you mean we would bundle the JS libs in the zotero package? If all the > source is there, it can go into "main". Still it's borderline, because library > bundling is bad practice, but maybe it could be acceptable as a temporary > solution.
I was thinking of the bundling solution. I think this was also discussed on debian-devel, and the conclusion was that the package had to go in contrib (because which would provide something which is different from the source: concatenated/minified/etc. js). >> More and more js libs get packaged, so when the ones with a lot of >> dependencies >> would have entered Debian, we can try to package the last ones. What do you >> think about this? > > That may be an option, though we have no control of whether this will happen > anytime soon. I know it's far from perfect, but I see no other reasonable solution :(. I don't know exactly how we would prepare the tarball with the bundle of the JS libs.
signature.asc
Description: PGP signature
