Feature #429
run-from-RAM install: Remember if certain package files have been deleted
| Status: | Rejected | Start date: | 09/09/2010 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Natanael Copa |
% Done: | 0% |
|
| Category: | Boot sequence | |||
| Target version: | - |
Description
A couple of users have had an interesting case where certain undesired configuration files included in the package APK would be deleted. However, if other files in the package APK are still needed, this raises a question of how to maintain the change over reboots.
Not sure what might be the best solution.
History
Updated by Jeff Bilyk over 1 year ago
Temporary workaround way could be to add an init script that deletes those files on boot-up. Not a long-term solution, but would get things started and as long as it's included in lbu would be persistent across reboots.
Updated by Natanael Copa over 1 year ago
What package was it?
For some packages we have a separate sample-config package to avoid this issue.
Other workaround is to not delete the files, just let them be empty.
Updated by Natanael Copa over 1 year ago
- Status changed from New to Rejected
I dont think we want any "smart" logic for remember what things got deleted. We should instead of delete things make it possible to not install the files in first place (i.e split the package).