Written by henk0775 the 5 May 08 at 14:03.
Category: System.
Related project:
Nothing/Others.
Status: New
Rationale
When you download your updates, you find it on a single server, or in many mirrors. But it is not so scalable. If Ubuntu users will grow, I can't realize the bandwidth needed.
Let developers build debs and distibuite it, with the help of community and packet mantainers. Ubuntu repository will be used for system and libraries, and, important, to CHECK AND PREVENT FROM CRACKING.
So the idea implies that mantainers will be closer to developers that now.
Another advantage is that, for example, googleearth.deb will be distribuited by google, checked by ubuntu/canonical, and you'll update it without reinstallations.
Thats why theres many ideas to encourage the use of apt-torrent, which uses bittorrent, which is VERY scalable, and does CRC chunk checking, and has the advantage of also being secure, and ready to deploy.
So I will vote for apt-torrent instead.. -1, sorry. I do agree with the idea, but in a way, apt-torrent is the same idea.
It's not the same idea. Imagine that you installed a program that stays in developers' server, checked by canonical, trought apt-torrent, and updated without adding a line in your source.lists. Apt should see a uri in the header of the packages.
So you want the current system, where anybody can create a .deb or a repository, but you want Ubuntu/Canonical to check that the .deb works properly? And then what happens, do they sign it? Or give them an "Ubuntu says we can write code" sticker for their Web site?
I wish that many apps you can find in universe will be moved in developers' site even if it was made by ubuntu mantainer. The porpouse is that tirdh party packages will work like a official ones. Canonical could certificate it. It's not like a police state.