Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

That would still be the case if the packages weren't 1-3 years out of date.


sort by: page size:

Yes, but they don't enforce it for new packages.

We're about 2 years out from having that work with most packages though, aren't we?

Which packages in particular? I've always found most things to be rather recent...

Not sure about five years ago, but these days it's usually not to bad for popular packages.

To get up to date packages?

Second, they screw up maybe 1 out of a 1000 packages in my experience.

I have years of data at my disposal. It's more like 2-5 packages out of 100. :-)


That says nothing about the distribution of the packages. That's pure speculation.

I know. Yet most folks take packages at face value as if it was a part of some standard library.

We've had the fixed versions of the packages for quite some time.

Tough call though, since # of packages is a poor metric.

At least with most packages this can't happen anymore.

If a package owner distributes a wheel, you're good. Most packages do now.


apt deciding it should yeet essential packages is not a new thing and has happened many times to many people.

one hundred and sixty thousand signed packages with ten+ years of history and of course, one bad one means the system is "weak"

As long as you don't get stale packages plagued by unfixed bugs.

I would never expect them to do that without vendoring the package. Which mitigates that risk.

What sorts of packages are these though? I've not had a single problem with anything practical in years.

It's still working very well for Amazon, and the company evaluated alternatives and choose to stick with packages because they have the right granularity.

Just in that there's a package already?

I don't see the connection. I didn't say that they have more packages, just that they have very good packaging tooling that makes it simple to make consistent packages.
next

Legal | privacy