Hi Hubert, Thanks for writing this down.
On 19-09-17 17:58, Hubert Chathi wrote: > https://wiki.debian.org/HubertChathi/JavaScriptPolicy > > Please let me know what you all think of it, and suggest > improvements/fixes/etc. I was wondering how you envision the following: "The source package name may also include the APIVERSION in its name." I mean, if the binary package should contain it, and there are multiple versions, shouldn't the source package also contain it? Or is this related to the last paragraph of that chapter? Also, I think we want some more words when the package with APIVERSION is "updated" with a newer version. I.e. I think it shouldn't be updated when you still want to provide the old APIVERSION, but instead there should be a new package. Or are you envisioning to provide multiple APIVERSIONs from the same source (I would recommend against that, although since the latest uscan version less so). Last time we discussed a target for how many APIVERSIONs are allowed. I don't remember quickly what came out of that discussion, but maybe having the discussion (or different opinions) reflected in the policy as point to consider may be appropriate. Paul
signature.asc
Description: OpenPGP digital signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel