Author: hawk Date: Tue Jun 10 09:35:26 2008 GMT Module: PLDWWW URL: http://www.pld-linux.org/Titanium?action=diff&rev2=26&rev1=25 ---- Log message:
---- Page affected: Titanium ---- Diffs: ================================================================ Other software: - * glibc 2.7 + * glibc 2.8 * gcc 4.2.x * KDE 3.5.x * Gnome 2.22.x @@ -53, +53 @@ == PLD Titanium FAQ == ''Q: Why you have created PLD Titanium?''[[BR]] - A: There were few reasons. First, I wasn't able to do some changes to PLD Ac without complete distribution rebuild and killing some architectures. Second: PLD Th is not stable enough for me. By stability I mean possibility of doing poldek --upgrade-dist on all of my systems with minimal risk that it will break something up. Third, I sometimes need some specific changes that I can't or rather I shouldn't put in official PLD. Creating my own fork was the only sollution for these problems. + A: There were few reasons. First, I wasn't able to do some changes to PLD Ac without complete distribution rebuild and killing some architectures. Second: PLD Th is not stable enough for me. By stability I mean possibility of doing poldek --upgrade-dist on all of my systems with minimal risk that it will break something up. Third: I sometimes need some specific changes that I can't or rather I shouldn't put in official PLD. Creating my own fork was the only sollution for these problems. ''Q: If you are the only one developing PLD Titanium, wouldn't it be out of date because you simply will not have enough time and resources to maintain it?''[[BR]] A: Its not like that. I'm not the only one developing PLD Titanium. I'm using official PLD CVS for building packages so in fact all PLD developers are maintaining Titanium :) I'm however the only person who can manage packages on FTP. @@ -62, +62 @@ A: The difference is mainly in management. I have my own idea how distro should be managed and I'm stick to it. There are some other differences too. Titanium has some additional packages that I need and few packages are in different versions/configuration so I don't need to build them manually for my systems. At the moment there are only few of them. ''Q: If I understand correctly, if you will need some change in Titanium you will simply do it no matter what it may break?''[[BR]] - A: Basically, yes, but its not that simple. Its true that I'm developing PLD Titanium for myself because I need such version of PLD. I'd have to do it anyway. Since I've chosen to share my work with world instead of keeping it just for myself I'm aware that I'm not the only one using PLD Titanium. Because of that, if I'm doing some special changes that only I require I'm trying to eliminate or at least minimize a danger it may cause to other systems. + A: Basically, yes, but its not that simple. Its true that I'm developing PLD Titanium for myself because I need such version of PLD. I'd have to do it anyway. Since I've chosen to share my work with world instead of keeping it just for myself I'm aware that I'm not the only one using PLD Titanium. Because of that, if I'm doing some special changes that only I require I'm trying to eliminate or at least minimize a damage it may cause to other systems. ''Q: Is it safe to use PLD Titanium?''[[BR]] A: Yes. As long as you don't use ready or test package trees you shouldn't have any special problems. You may encounter same problems (or even more of them) when using official PLD or any other Linux distribution. Even if you will use some packages that I modified for myself you may reconfigure them the way you want. If this is not enough you may of course build you own packages with your own configuration using PLD CVS. @@ -142, +142 @@ * xorg-driver-video-nvidia.spec * xorg-driver-video-nvidia-legacy.spec * xorg-driver-video-nvidia-legacy2.spec - * zaptel.spec First sent them normally so they'll build for regular kernel and with userspace. Then send them for each PLD Titanium kernel using auto tags. For example: _______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
