> Yes, it's possible that there could be a problem with a package you didn't know existed My limited experience may well be the exception, but I'll bring it u

> Yes, it's possible that there could be a problem with a package you didn't know existed My limited experience may well be the exception, but I'll bring it up anyway. I wrote an RSS module in 2003. Someone else later added it to PyPI, the Python indexer. It has also been distributed by multiple packaging systems. I had no clue. No packager has ever said anything about it to me. Looking now, it's distributed by Gentoo, Debian, Slackware, Ubuntu, and more. It's also used in PyMediaRSS2Gen, dilbert-rss, and loads more packages. It took me two days to write that package, and another few days of maintenance in the 12 years. Until now I believed this hand-off mechanism, mediated by PyPI, was the way to go. Because it would take me much longer to interact with all of those distributions than to write the code in the first place! > Why not give some [doubt] to the packagers? Because the statement you made earlier, "They need to work with package maintainers, fixing (and not re-creating) problems that make packaging difficult. Anyone who can't do that, or isn't willing to, can't claim to have "learned all they can" about software delivery, as I see in the first paragraph of the other Taskwarrior article posted today." gave no doubt to the developers.