3 ms·
> In most situations, this is truly a trivial amount of investment relative to the overall cost of developing and maintaining an application. I wouldn't say th
by mercurial 12y ago
> In most situations, this is truly a trivial amount of investment relative to the overall cost of developing and maintaining an application.
I wouldn't say that creating and owning packaging for, say 50 libraries (assuming you only deploy to a single platform) represents a "trivial amount of investment" for a standard small developer team.
- jkyle 12y agoHonestly, if a particular development environment for a project required tracking 50 libraries not supported by any distro community and my development team was so small that I couldn't do that in a sane manner... I might reevaluate the suitability of that particular language for the project. On a side, it only takes marginally more time to build a package for a distro as it does to build the package by itself. If you've already got the build done, 3 experienced guys could knock out 50 packages in a week. Inexperienced (in this task), but competent, devs should be able to do it in 2 weeks.