I accidentally removed "wayland" using the "Remove Builtin Packages" app in BionicPup64 (frugal install on hard drive) is there any way to gracefully recover from this stupidity?
Removed "wrong" builtin package
Moderator: Forum moderators
- mikewalsh
- Moderator
- Posts: 6441
- Joined: Tue Dec 03, 2019 1:40 pm
- Location: King's Lynn, UK
- Has thanked: 954 times
- Been thanked: 2121 times
Re: Removed "wrong" builtin package
@WoodLark :-
Mm. I don't know about 'graceful' - lololol - but so long as you know which files you accidentally removed, it should be a simple matter of mounting the original ISO, and just copying the files across. Unless, of course, this was something you installed yourself from the PPM, or as part of another package.....in which case, it would then be a part of your save-file/folder contents.
If you make regular backups, again, it should just be a case of mounting/opening your backup and copying the relevant files across. AFAIK, Puppy doesn't have any GUI- or app-based way to recover from this kind of 'cock-up'; it's definitely going to be a manual replacement job.
It MAY be possible to reverse the 'white-listing' that Puppy employs for the removal of built-in packages. As I understand it, there's no actual 'removal' involved; it couldn't happen anyway, since under normal circumstances Puppy loads from 'read-only' sources, as you know. I believe what Puppy does is to remove the 'indexing' for the relevant files, so the file-system no longer sees them..? I could be wrong, of course.
Others may have alternative suggestions to offer. We'll get ya sorted.
Mike.
Re: Removed "wrong" builtin package
I was able to fix it by rebooting then re-installing wayland and its libraries. This probably is not the "best" way to fix the issue, but it does appear to have worked.
- mikewalsh
- Moderator
- Posts: 6441
- Joined: Tue Dec 03, 2019 1:40 pm
- Location: King's Lynn, UK
- Has thanked: 954 times
- Been thanked: 2121 times
Re: Removed "wrong" builtin package
WoodLark wrote: Tue Dec 01, 2020 4:53 pmI was able to fix it by rebooting then re-installing wayland and its libraries. This probably is not the "best" way to fix the issue, but it does appear to have worked.
Hey! if it works (and keeps on working).....why worry? Pup's all about the "unorthodox", after all..!
Good that you got it fixed.
Mike,