Revisit the backports modules package
Registered by
Ben Collins
The linux-backports
Blueprint information
- Status:
- Complete
- Approver:
- Ben Collins
- Priority:
- Undefined
- Drafter:
- Tim Gardner
- Direction:
- Needs approval
- Assignee:
- Tim Gardner
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Tim Gardner
- Completed by
- Tim Gardner
Whiteboard
2007-11-20 BenC: Just a minor nit. Give some reasoning behind the -<release> meta package name change (basically to stop forced usage of lbm across release-to-release upgrades).
2007-22-20 rtg: Maybe you should explain it because I'm pretty happy with the way things work, and I don't understand what you are wanting. Prior to a dist-upgrade the user has to edit sources.list. If they choose to leave backports enabled, then they get upgraded when an lbm package is created after release.
(?)