Clean-up too old packages
Few writes "One more question. What happens if a newer texlive version shows up and gets installed? The (now possibliy outdated) g-ctan packages still shadow the versions installed by the texlive package. This means I have to clean them up my self, right? If so it might be good idea to have a clean up option for g-ctan (when the version check you wrote about somewhere else is ready). And maybe the texlive ebuild should check if g-ctan packages are installed and warn about it."
So this leads to the following behaviour:
* Collect ebuilds in g-ctan.
* Check version number and compare with G_RELEASE_REVISION.
* Inform user about it.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Christian Faulhammer
- Definition:
- Approved
- Series goal:
- Accepted for 2009
- Implementation:
-
Implemented
- Milestone target:
-
2009.1
- Started by
- Christian Faulhammer
- Completed by
- Christian Faulhammer
Whiteboard
How to do it:
* find G_OVERLAY_
* extract file name (without directories) and ebuild suffix.
* loop over names
** extract PN and PV
** test if PN is in package name database -> queue for removal if not, continue loop
** test if PV is less than G_RELEASE or PV from database -> queue for removal, continue loop
* display all to be removed, ask for confirmation
* loop over all PN-PV
** delete, give output when error but do not exit
