Recent Features
| |||||||||||||
Camp KDE: Using Slackware to investigate KDE 4Camp KDE: Using Slackware to investigate KDE 4Posted Apr 7, 2011 23:25 UTC (Thu) by dag- (subscriber, #30207)Parent article: Camp KDE: Using Slackware to investigate KDE 4
It's funny how he indicates that using --force can lead to problems one cannot easily recover from.
Well, without dependency tracking, you pretty much have the same problems as using --force all the time, only thing is that you don't know what problems you might have until you run into them.
It's like blindfolding, it gives you peace up to the moment you start walking around. As long as you don't hit anything, you're fine !
I guess he hates spending time doing proper packaging and prefers to debug those problems by himself. If that's what you like, great. Some people compile all their stuff with their own compile flags and they are happy with that. It doesn't mean it is a smart or pragmatic solution for anyone else.
(Log in to post comments)
Camp KDE: Using Slackware to investigate KDE 4 Posted Apr 7, 2011 23:41 UTC (Thu) by dlang (✭ supporter ✭, #313) [Link]
the way most packaging systems work is that if you stay within the system, things work fairly well, but if you only partially work outside the system you end up working not only against the technical problem, but also against the packaging system itself.
so if you are straying too far from the base, it can be easier to work completely without the packaging system than trying to work around it all the time (and especially, preventing it from being "helpful" in ways that break your system)
Camp KDE: Using Slackware to investigate KDE 4 Posted Apr 8, 2011 0:31 UTC (Fri) by magila (subscriber, #49627) [Link] FWIW I've found that the Paludis package manager used with Exherbo/Gentoo is pretty good at allowing the kind of experimentation described in the article. In particular via the "cave import" command.
Camp KDE: Using Slackware to investigate KDE 4 Posted Apr 11, 2011 10:27 UTC (Mon) by roblucid (subscriber, #48964) [Link]
Yep. I've recovered RPM based systems using the chroot environment using a different distro's Live CD, which I just had to hand. I think it was glibc & ldd which I managed to screw up. Usually when ppl claim something is hard to do with rpm(8), it's because they couldn't understand the man page or lacked the stamina to find the right piece.
openSUSE supported installing both KDE3 & KDE4, thought it was best to experiment with KDE4 under a different username to avoid trouble going back to KDE 3.5, which the packaging without dependency solution also fails to address.
|
|||||||||||||