Brian Masinick
I agree; to be certain, that’s the way I have chosen and so far it has worked out well.
I spent a lot of time with the antiX setup yesterday. Since I am updating each of my systems I spent solid time with MX Linux, where I also used the @Wallon approach. MX Linux is also responding well to the most recent updates too.
The way I understand, your (and @Wallon, of course) approach is more general. In principle it should work for any Debian based distro. So far I implemented the antiX specific approach only, although I may not see the latest versions of updates as they become available. Also for MX Xlibre I may have to adopt yours (and @Wallon) approach, depending on availability of XLibre in MX repo…
As we’ve been discussing today, DON’T use the XLibre Debian style approach if you want to keep antiX clean; with Debian and MX Linux, which don’t keep out libelogind anyway, I DO recommend the very newest version; it’s very nice, but it WILL taint antiX, so unless you’re willing to do that, keep away from it there. I fixed it; I went back to Xorg, removed the extra repo, rebooted, and started over; it cleaned out the libelogind stuff; that’s the first thing I checked.
All of this HAS been a good, helpful exercise. I’m thankful for everyone who is participating in this discussion and I especially thank @anticapitalista for bringing in clean XLibre packages and for @Wallon for introducing and explaining the possibilities to us.
Though this stuff is very good, I still caution the average person who isn’t aware of the implications to steer clear. I hope in time we can make all of this the default; meanwhile, leave it to the experimenters to work with it, get it working really well, and when it’s stable enough MAYBE it’ll eventually become an antiX standard. Meanwhile, leave it to those who know how to repair their messes!
--
Brian Masinick
Alternate "Search B":
This search page