On Tue, Sep 29, 2026 at 2:45 PM Jonas Smedegaard <[email protected]> wrote: > No, I have not checked the code.
Please have a look so that you can answer my question correctly. > It is permitted to package dead-end tools to "infect" users' systems > with non-Debian tools, but what is your point in doing that? You cannot > package any code that _needs_ vue if that package is only available > through pulling it in from an external source. > > An example of dead-end helpers is the official Debian package rustup > which is nice and convenient for users *not* caring about source, but > totally useless for Debian developers for packaging anything depending > on that side-installed tool. > > So back to your original question: Why do you ask? What is the aim? Thank you for checking my original question. My main goal is to build web front for a golang package. The is a missing build-deps on vue3. Jermeny suggest to update vue.js 2.7 to version 3.5 in Debian, and you asked me to make sure all the reverse-dependency such as python-trame-client works correctly with updated vue.js versoin 3.5. And my original question here: I wanted to ask if the way python-trame-client currently handles its web app is fully compliant with Debian policy. If this approach is acceptable, I am hoping to follow the same method to build the web frontend for the golang package, which would save me from having to package all of the missing Node.js build-deps from scratch. Best regards, -Andrew
