The connection was lost. Trying to connect again.
This thread continues with a post that is not available on this server. Open the original post
@eschwartz @ftranschel Yeah, apart from nixos. I accept that I probably done goofed but the specific update I left running over night and in the morning I shutdown without taking the time to read it as I had to start work.
This isn鈥檛 a Gentoo issue honestly, more of a me issue, I just want both stability and up to date packages without having to work too hard for it and nix just kinda supports that in a very ergonomic way imo.
Ok but I still don't understand how the existing configuration would be *wiped*. It should never be wiped. The worst case scenario is that the newly installed version doesn't accept the configuration file from the old version, which is a bad idea in general for the package's upstream to do.
Even then it could be "worked around". The package maintainer for greetd should add a pkg_pretend that prints a warning and sleep 5, and/or a news item should be added.
ewarn "As of dev-lang/perl-5.38.2-r3, the useflags debug, ithreads, quadmath move into"
ewarn "a use-expand variable PERL_FEATURES, which should be set globally in make.conf."
ewarn "It appears that you have not set this variable properly yet."
ewarn ""
ewarn "Giving you a chance to abort and read the corresponding news item now..."
for n in 10 9 8 7 6 5 4 3 2 1 ; do
echo -n "${n} "
sleep 2
done;
echo "continuing."
(This is guaranteed to run before any packages start to install, intended to do dependency-calculation-time sanity checks.)
@eschwartz Yeah, I can definitely see myself ignoring that. Its totally on me, but that's essentially what I'm saying. Nix does protect from this.
@MauriceElliott @eschwartz I totally get this, I have goofed more configs than I care to admit. However, for me personally the opportunity costs of #nixos would absolutely not outweight the opportunity costs of 'eselect news read' once in a while...