@mpt If I understand correctly, the backports repo contains new versions of software already included in the main Ubuntu repos. What I am suggesting is:
1: Do away with the Ubuntu Backports repo entirely. 2: Create two separate repos: one for Ubuntu applications (and perhaps even commercial applications could be included here, but I'm not sure the legal implications. If not, then split the Applications repo into one for FOSS software, the other for proprietary) 3: and the other for the core Ubuntu system, eg kernel, core libraries and system components. 4: The Ubuntu applications repo would have a rolling release style of updating, 5: while the Ubuntu Core repo would keep it's current 6 month release model. There would be no overlap of packages in the Core repo, and the Applications repo. As far as getting software easily into the Applications repo, in order to prevent your first point, why couldn't the community review the software? There could be a "Community Review" site where packages seeking admission to the application repo could be uploaded. Anyone could register easily to the review site and vote on a package's safety. Their voting weight would be in proportion to their reputation. Reputation could be earned by the accuracy of ones votes. Voting "safe" for a package that was eventually turned down as malicious would lower a user's reputation, thus decreasing their voting weight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/578045 Title: Upgrading packaged Ubuntu application unreasonably involves upgrading entire OS To manage notifications about this bug go to: https://bugs.launchpad.net/null/+bug/578045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
