Le Mardi, Octobre 22, 2019 12:03 CEST, Jonas Smedegaard <jo...@jones.dk> a écrit: > Quoting Xavier (2019-10-22 11:32:19) > > Le Mardi, Octobre 22, 2019 11:15 CEST, Jonas Smedegaard <jo...@jones.dk> a > > écrit: > > > Quoting Xavier (2019-10-22 10:01:11) > > > > Le Mardi, Octobre 22, 2019 09:10 CEST, Julien Puydt > > > > <julien.pu...@laposte.net> a écrit: > > > > > If you want to have ts-node, why not package it properly, with a RFP > > > > > or ITP? > > > > > > > > > > I don't see the point into packaging those together... > > > > > > > > > > JP > > > > > > > > It was an attempt to avoid waiting 6 or 7 months in the NEW queue > > > > with a 50% chance of getting an acceptance or never getting an > > > > answer (which seems to be considered as a rejection, see > > > > node-mimelib for example). > > > > In node-sinon packaging, we decide to embed @sinon ecosystem to > > > > avoid this. I thought we could consider ts-node as part of the > > > > typescript ecosystem. > > > > > > > > Then OK, I'll ITP and continue to embed ts-node in some > > > > packages... > > > > > > Please do *not* hide code from ftpmasters by embedding it in other > > > packages - that is foul play, and you risk getting banned from > > > Debian! > > > > Remember that embedding is a requirement from ftpmaster. I don't hide > > anything in my package and I follow all the rules I know. > > Great! > > > > But if you think my work is bad, please denounce me and ask for my > > immediate expel ! > > What I try to communicate above is that it seems you are missing a rule > when you describe avoiding NEW queue as a reason for embedding. > > (sure there are _other_ reasons for _sometimes_ embedding)
Like tsc, ts-node is used during build or test. I already pushed packages in new queue with build or test components embedded and ftpmaster accepted them (I always put test component in debian/tests/test_modules), same during Buster freeze: I fixed some problem and enabled test using embedded components : it has been reviewed and accepted by release team. Many packages are missing to enable upstream tests in our packages. If this group decide to ban embedding test and/or build modules, many of our packages must be updated (disable tests) or removed from Debian (not only mines !). Personnaly I think that we should enable test anywhere it is possible to provide quality packages. That's why I prefer embedding than pushing package without test. The trouble came when ftpmaster asked us to stop packaging separately and group package. Initially for "little" components, but some not-so-little where also rejected. I worked on uscan and pkg-js-tools to propose some workaround to this new requirement. The idea here was to group ecosystems to follow ftpmaster new requirement. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
