AptURL Policy Discussion
Discussion on the policy of using apturl
Blueprint information
- Status:
- Complete
- Approver:
- Colin Watson
- Priority:
- Medium
- Drafter:
- Michael Vogt
- Direction:
- Needs approval
- Assignee:
- Michael Vogt
- Definition:
- Review
- Series goal:
- Accepted for karmic
- Implementation:
-
Implemented
- Milestone target:
-
karmic-alpha-3
- Started by
- Michael Vogt
- Completed by
- Steve Langasek
Whiteboard
apt-url-policy on gobby
This is rickspencer3:
I feel strongly that:
1. It should be much easier than it is for developers to get their apps to users, and it should be much easier for users to install such software. PPAs is potentially good way to do this. Finding PPAs and exchanging keys should be much easier.
2. The way that users get PPAs (or whatever the solution is) should be very separate (but still easy) from the way that users install software that has run the relevant Ubuntu gauntlets.
As I said I would, I've compiled some mock-ups of what I was talking about at the session:
http://
See also https:/
Implementation status:
1. software-properties fetches a ppa key automatically when adding a ppa
2. software-properites "Third-Party/Add" supports shorthand "ppa:name" syntax (and auto-key fetching)
3. there is a commandline tool "add-apt-
4. update-manager shows the origin for packages comming from a PPA
The display of PPA changelogs is blocked on https:/
The auto-adding of depedant PPAs is blocked on https:/
I set this to beta-available for the software-properties improvements.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
