Le 07/09/2018 à 16:36, Xavier a écrit :
> Le 07/09/2018 à 13:38, Bastien ROUCARIES a écrit :
>> On Thu, Sep 6, 2018 at 9:45 PM Thorsten Alteholz <deb...@alteholz.de> wrote:
>>> Hi Bastien,
>>> On Wed, 5 Sep 2018, Bastien ROUCARIES wrote:
>>>>>   - put together packages that belong together; I am not sure here, but
>>>>>     wouldn't it be fine to have just one package node-d3 or node-babel
>>>>>     that contains all corresponding modules (though their different 
>>>>> versions
>>>>>     might create problems in keeping track of them)?
>>>> I strongly oppose to keep different version.#
>>> I don't meant to have different versions of one package here, but
>>> bundling several packages with different versions, so that it might not be
>>> clear what version the resulting package might get.
>> I agree with this maybe we could get something like:
>> mainpackage+embded-nameembded1-version+embded-namembdedversion2-version+version
>> ?
>> Bastien
> Hello,
> I've written a little draft:
> https://wiki.debian.org/Javascript/GroupedSourcePackageProxy

I've updated draft to build a stateless proxy: DB was a bad idea since
it can be modified at each request.
I started to build groupedsources.cgi. The function to build grouped
upstream sources works. Now I'm going to write the download part. When
ready, you will be able to test with node-tap, simply by changing

If this proposition is acceptable, I'll propose a policy patch to
authorize JS grouped sources and a JS policy patch for details.


Pkg-javascript-devel mailing list

Reply via email to