Installing a non-repository package that exists only to add another repository is a clever hack, but still a hack. Ubuntu policy is currently that it should be non-trivial to add a PPA as a repository, on the grounds that damage from software in unreliable PPAs would reflect poorly on Ubuntu. It would be counterproductive for Launchpad developers to try and subvert Ubuntu developers this way (especially while Ubuntu is the only OS for which Launchpad builds PPA packages).
Ubuntu has a whitelist for trusted repositories, and a process for being added to that whitelist <https://wiki.ubuntu.com/ThirdPartyRepositoryApplicationProcess>. The Ubuntu One developers should apply for inclusion in the whitelist, instead of using a .deb hack. The same is true for any other PPA owner who wants easy installation but for whom the official Ubuntu repositories are inappropriate.
Installing a non-repository package that exists only to add another repository is a clever hack, but still a hack. Ubuntu policy is currently that it should be non-trivial to add a PPA as a repository, on the grounds that damage from software in unreliable PPAs would reflect poorly on Ubuntu. It would be counterproductive for Launchpad developers to try and subvert Ubuntu developers this way (especially while Ubuntu is the only OS for which Launchpad builds PPA packages).
Ubuntu has a whitelist for trusted repositories, and a process for being added to that whitelist <https:/ /wiki.ubuntu. com/ThirdPartyR epositoryApplic ationProcess>. The Ubuntu One developers should apply for inclusion in the whitelist, instead of using a .deb hack. The same is true for any other PPA owner who wants easy installation but for whom the official Ubuntu repositories are inappropriate.