PLDWWW: Titanium

hawk hawk at pld-linux.org
Mon Apr 28 19:04:13 CEST 2008


Author: hawk   Date: Mon Apr 28 17:04:13 2008 GMT
Module: PLDWWW   URL: http://www.pld-linux.org/Titanium?action=diff&rev2=20&rev1=19
---- Log message:


---- Page affected: Titanium

---- Diffs:

================================================================
  Conjunction of new software with stability. There will be no freezing, no releases, no versioning. Whenever you will install PLD Titanium you will get up to date and stable system (unless you are using ready or test package trees).
  
  Available kernel versions:
+ 
   * kernel 2.6.22.x with Linux Vserver 2.3.x, minimal grsecurity and dozens of other patches (default)
   * kernel 2.6.22.x with Linux Vserver 2.3.x, full grsecurity and dozens of other patches
   * kernel 2.6.22.x for desktop PCs
@@ -24, +25 @@

   * kernel 2.6.22.x with Linux Vserver 2.3.x, minimal grsecurity and some driver updates only
  
  Other software:
+ 
   * glibc 2.7
-  * gcc 4.2.3
+  * gcc 4.2.x
-  * KDE 3.5.9
+  * KDE 3.5.x
-  * Gnome 2.22
+  * Gnome 2.22.x
   * XFCE 4.4.2
-  * ... more will be added when packages will be ready
+  * OpenOffice.org 2.2.x
  
  == Distribution status ==
  
- System is fully usable but number of packages is limited to those needed by developers. There are currently over 6000 rpm files for each binary architecture and over 1000 of noarch packages. If someone need more packages to be included in distribution he has to poke some developer who can build packages for Titanium to process his request. Help in preparing and building packages is welcome :) To see who is able to build packages check [http://cvs.pld-linux.org/cgi-bin/cvsweb/PLD-doc/PLD-who_is_who PLD who is who].
+ System is fully usable but number of packages is limited. There are currently over 6000 rpm files for each binary architecture and over 1000 of noarch packages. If someone needs more packages to be included in distribution he has to poke some developer who can build packages for Titanium to process his request. Help in preparing and building packages is welcome :) To see who is able to build packages check [http://cvs.pld-linux.org/cgi-bin/cvsweb/PLD-doc/PLD-who_is_who PLD who is who].
  
  Installation is possible using [http://cri.pld-linux.org/ CRI] or manually using [ftp://ftp1.pld-linux.org/people/hawk/cri/chroots/ CRI chroots].
  
@@ -48, +50 @@

   * build new packages if necessary or if requested by other users
   * fix bugs (be sure to report them on PLD Bugzilla using link below, bugs reported by mail or jabber may be ignored)
  
+ == 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.
+ 
+ ''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.
+ 
+ ''Q: So if you are using same stuff as PLD then what is the difference between Th and Titanium?''[[BR]]
+ 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.
+ 
+ ''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.
+ 
+ ''Q: Is there a risk that you will abandon PLD Titanium some day?''[[BR]]
+ A: Generally, yes. I can't tell what changes future will cause in my life. However as long as I'm using Linux I will support PLD Titanium in my spare time. But even if I'll abandon PLD Titanium at some point then any PLD developer may take it over and continue my work.
+ 
+ If you have any other PLD Titanium related questions, please contact me directly. Check [:hawk:my personal page] for details. Most frequent questions will be added here.
+ 
  == Links ==
  
   * [http://ep09.pld-linux.org/~pldti/ List of broken dependencies and FTP/CVS version/release comparison] for PLD Titanium.
   * [http://bugs.pld-linux.org/ PLD Bugzilla where you may report PLD Titanium bugs]
  
- == Notes from Hawk ==
+ == Notes from Hawk to PLD developers interested in PLD Titanium developement ==
  
  If you are PLD developer and you want STBR permission, let me know. Also please read few rules below before doing actual developement in PLD CVS or sending build requests.
  


More information about the pld-cvs-commit mailing list