On Sun, 10 Sep 2017 09:03:01 -0400, Jude DaShiell wrote:
>So far as I know, pacman's cache was left untouched by the script.
IIUC it shouldn't matter, you got rid of all configs (excepted of those
in $HOME) after removing the packages, with or without the -n option.
Unlikely the packages in the ca
On Sun, 10 Sep 2017 12:37:48 +0200, Guus Snijders wrote:
>Did your script also delete pacman's cache? Otherwise it would have
>been there in /var/cache/pacman/pkg (from the top of my head).
Hi,
assuming it anyway is the same package version and release, then it
makes no difference if the package
So far as I know, pacman's cache was left untouched by the script.
On Sun, 10 Sep 2017, Guus Snijders via arch-general wrote:
Date: Sun, 10 Sep 2017 06:37:48
From: Guus Snijders via arch-general
To: General Discusson about Arch Linux
Cc: Guus Snijders , arch-gene...@lists.archlinux.org
Subjec
Op 10 sep. 2017 11:41 schreef "Jude DaShiell" :
I discovered this and was able to recover, and think gnome could do with a
fix.
You do sound a bit mysterious here :).
Apparently you discovered something, but don't tell what it is. Kudos for
capturing attention, but don't expect a fix for anythin
I discovered this and was able to recover, and think gnome could do with a
fix.
I put together a script to completely erase gnome from this system and for
the most part that script worked really well. The exception was that it
also removed wpa_supplicant since I had cascading and recursive and
5 matches
Mail list logo
