-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perl-cleaner problem #8
Comments
You could simply run |
Dear Sakaki,
Thank you very much for your response, I will change my cronjob this way.
Your work is awesome!
Diego
2018-03-16 10:57 GMT+01:00 sakaki <notifications@github.com>:
… You could simply run genup with the -p (--no-perl-cleaner) option to
avoid calling invoking perl-cleaner as part of the process. Then, every
so often (if you wish) invoke perl-cleaner manually.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/sakaki-/sakaki-tools/issues/8#issuecomment-373662108>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASWVlAV4yxn9kT5GZ_w16sspJQKpiLUYks5te4yfgaJpZM4SoiDX>
.
|
31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the ebuilds etc. may be of use to others); however, I plan no further updates, nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice. |
Dear Sakaki,
Thank you for sharing this tools.
I use your repo sakaki-tools (efi system) and I noticed a problem that apparently has no solution:
pearl-cleaner (called by genup) is allways rebuilding some packages (in my case, texinfo, rxvt-unicode, weechat). As I have a cron job (daily) for genup and also an SSD drive, I am worried about it.
I know it is not about your script, but the forum seem not to worrie about this problem and I also assume it could be risky for solid state drives on the long term (at least it is annoying). Genup is wonderful and I want to keep using it.
Do you have any suggestion?
Thank you in advance,
All the best,
Diego Samuelle
The text was updated successfully, but these errors were encountered: