From: bo0od <bo0od@riseup.net>
To: 47846@debbugs.gnu.org
Subject: bug#47846: Feature Request: Add ability to disable having cache or generations
Date: Sat, 17 Apr 2021 18:29:56 +0000 [thread overview]
Message-ID: <df61f8dd-ca00-a419-a751-46d39b1c9f00@riseup.net> (raw)
Hi There,
Current situation with the guix distro upgrade is:(as i understand)
A) User Packages: whenever there is an upgrade to package A version 1 to
new Version lets call it A version 2 , So the process is ADD A2 → SWITCH
to A2 → Cache A1 and so on.
B) System Packages: Same process but it will be saved through generations
This causes unpleasant actions to some users:
- Bloating the disk size
- Having old unnecessary files/packages
- Questionable security of the saved old versions. As it depend if they
have access to suid or not (i didnt investigate this, but if they have
then thats big problem but this is not the ticket to discuss it)
I know someone would jump in and say but roll back is great feature and
its useful and....i know that but like i said might be not suiting all
users (specially with limited space).
Current manual solution is to delete this extra mess using 2 commands:
guix gc -d 1s && sudo guix system delete-generation
This should be run whenever there is no space left, Or to get rid of the
old stuff
My suggestion is to have the ability to make Guix automatically just
having the latest up to date packages without extra consumed storage (no
cache no generation no nothing more than having the latest packages
available in the distro).
So the process is ADD A2 → SWITCH to A2 → Delete A1 , Or Download A2 →
Replace over A1 and so on.
ThX!
next reply other threads:[~2021-04-17 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 18:29 bo0od [this message]
2021-04-17 19:24 ` bug#47846: Feature Request: Add ability to disable having cache or generations Leo Famulari
2021-04-17 20:05 ` Leo Prikler
2021-04-18 14:40 ` bo0od
2021-04-18 15:39 ` Leo Prikler
2021-04-18 18:45 ` bo0od
2021-04-18 19:28 ` Leo Prikler
2021-04-19 18:02 ` bo0od
2021-04-17 20:07 ` Maxime Devos
2021-04-18 10:00 ` Maxime Devos
2021-04-18 17:43 ` bo0od
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df61f8dd-ca00-a419-a751-46d39b1c9f00@riseup.net \
--to=bo0od@riseup.net \
--cc=47846@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).