Better release channel management

Registered by Sergey "Shnatsel" Davidoff on 2011-11-22

There were complains about some dependencies for packages in the daily PPA being outside the PPA. We should determine the best way to maintain the PPAs so they don't become a nighmare for neither developers nor early adopters, and use upstream repos as much as possible.

Blueprint information

Status:
Started
Approver:
elementary core
Priority:
Medium
Drafter:
None
Direction:
Approved
Assignee:
Sergey "Shnatsel" Davidoff
Definition:
Approved
Series goal:
None
Implementation:
Good progress
Milestone target:
None
Started by
Sergey "Shnatsel" Davidoff on 2012-02-24

Whiteboard

See full specification for details.

I've developed a custom version of ppa-purge that can be called from maintainer scripts in .deb packages; see linked branch.
I've also requested importing and building apt-queue which was designed by JoliCloud for this exact use case, but I think using aptdaemon is a better idea.
~shnatsel

I've written a script that generates release channel packages. I've never tested those packages tbh, but they are supposed to add required PPAs and request a package lists update on installation and remove and purge those PPAs on removal. PPA signatures are not yet handled, though. ~shnatsel

Ok, I've rewritten the hell out of that script, it now handles keys and should also handle changes in PPA set properly. But it still needs more testing. ~shnatsel

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.