Nilson F. Silva
81-3036-0200 81-991616348 81-98546-9553 ________________________________ De: Yadd <y...@debian.org> Enviado: segunda-feira, 18 de setembro de 2023 11:10 Para: Nilson Silva <nilsonfsi...@hotmail.com> Assunto: Re: built-in packages: esniff in tad On 9/18/23 17:41, Nilson Silva wrote: > Hi Yadd! > >> Another thing: do you sponsor nodejs starter packs? > ! > Thank you in advance for your attention to my email. > > Answering your question: > I don't know if esniff is still an active project, as it hasn't been updated > since 2016. > And I also don't know how you keep up with the supposed updates that the > package will undergo. > > But perhaps this is a good reason for disincorporation. > > Another reason would be the issue of packages that depend on esniff. > > I actually got to this package, after running > npm2deb depends on -b -r > and I discovered that it is a dependency on the package I was bringing to > Debian. > > So I spent the end of the week working on it. Do you know `pkgjs-depends` ? Very helpful for such search > Since tad is a mandatory dependency of esniff, I found that the two cannot > coexist > in the same environment. But after all the packaging work. I still don't understand what you want to do > I believe the CI/CD test detected the problem in autopkgtests > > Now my concern would be: > What if someone else has the same problem as me? package something that also > depends on esniff, but don't know that esniff is a "tad" module? Ftpmasters asked us to no more package "too-little node module". Then we started to embed little package in bigger ones but in this case, the global package exports all names. Then you can require node-esniff in any debian/control. Then even if we disassemble the package to have a separate node-esniff, no changes. For now, node-tad isn't used by any package, neither esniff. So multiplicating source packages without real use isn't interesting. > I understand your concern as it is a crucial dependency for "tad". But if you > decide to cancel the incorporation, you can also co-maintain the package with > me. JS Team is a team, I'm not owner of any package. > If you obviously want to. > > But far be it from me to create controversy on this subject. > What can I do, and put the "pad" with Build-depends of the package I want to > bring to Debian? > > and by the way, if you can sponsor. Thank you very much! What is your goal with esniff ? Is it a need for building an interesting package ? > Nilson F. Silva
