3 ms·
Hey, I was just saying that that's the common idea, not that I think that way. Personally, I use NPM because NPM does local versioning, so I will never end up
by qwertyuiop924 11y ago
Hey, I was just saying that that's the common idea, not that I think that way.
Personally, I use NPM because NPM does local versioning, so I will never end up in dll hell.
Also, NO, NEVER WRITE A PACKAGE THAT HAS EXPLICIT KNOWLEDGE OF A DISTRO PACKAGE MANAGER. If you do, you are being an asshole. If you want to depend on a distro specific package manager, document your dependencies, and just expect them to be there. Because not everybody uses your package manager.
- dozzie 11y agoIf you have proper package building rules (not this currently popular fpm nonsense, which produces broken RPMs and DEBs unless one puts much effort in using it), tearing building procedure apart and adjusting it for other package managers will be really easy. No, you're not being an asshole. And if you want to be it even less, write a proper makefile and call that from package build rules (RPM spec, debian/rules, ebuild, or anything else).
- qwertyuiop924 11y agoYou should be writing Makefiles, or Scons, or whatever your build system is.