Author: hawk   Date: Fri Aug  7 16:56:57 2009 GMT
Module: PLDWWW   URL: 
http://www.pld-linux.org/Titanium?action=diff&rev2=40&rev1=39
---- Log message:


---- Page affected: Titanium

---- Diffs:

================================================================
  ||Stable||PLD||Current stable version of system also referred as "Main".||
  ||Pre-stable||ready||Packages scheduled to be moved to stable tree. They 
should work ok, but remember they aren't stable yet. Use with care. All 
packages must reside for at least one week in this tree (except for critical 
updates).||
  ||Development||test||Unstable versions of packages. They may contain severe 
bugs or even not work at all. Use at your own risk as you may completly crash 
your system!||
+ ||Archive||archive||Previous stable versions of packages from PLD tree. If 
new version somehow doesn't work you'll be able to downgrade quickly.||
+ ||Obsolete||obsolete||Packages that are no longer officialy supported by PLD 
Titanium.||
  
  Available kernel versions:
  
   * kernel 2.6.27.x with Linux Vserver 2.3.x, full grsecurity, apparmor and 
some other patches (default)
   * kernel 2.6.27.x with just full grsecurity
   * kernel 2.6.27.x with just Linux Vserver 2.3.x and minimal grsecurity
-  * vanilla kernel 2.6.27.x
+  * vanilla kernel 2.6.30.x
+  * dedicated desktop/laptop kernel 2.6.30.x
  
  Other software:
  
-  * glibc 2.8
+  * glibc 2.10
   * gcc 4.3.x
-  * KDE 3.5.x
+  * KDE 4.3.x
-  * Gnome 2.24.x
+  * Gnome 2.26.x
   * XFCE 4.4.3
   * Open``Office.org 2.4.x
  
  == Distribution status ==
  
- System is fully usable. There are currently over 7200 rpm files for each 
binary architecture and over 1700 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].
+ System is fully usable. There are almost 8000 rpm files available for each 
binary architecture and almost 1700 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].
  
@@ -116, +119 @@

   * kernel-vanilla.spec:Titanium
   * kernel-bare-vserver.spec:Titanium
   * kernel-bare-grsecurity.spec:Titanium
+  * kernel-desktop.spec:Titanium
+  * kernel-desktop.spec:Titanium --with laptop
  
  When auto-ti tags are created please send following kernels using their auto 
tags to i686 builder:
  
@@ -123, +128 @@

   * kernel-vanilla.spec --with pae
   * kernel-bare-vserver.spec --with pae
   * kernel-bare-grsecurity.spec --with pae
+  * kernel-desktop.spec --with pae
+  * kernel-desktop.spec --with laptop --with pae
  
  When all kernels are ready all kernel modules must be recompiled. Following 
specs must be rebuilt:
  
   * Virtual``Box.spec
-  * atl2.spec
+  * atl2.spec (only for 2.6.27.x kernels)
+  * dahdi-linux.spec
   * e1000.spec
   * e1000e.spec
   * igb.spec
@@ -139, +147 @@

   * svgalib.spec
   * xorg-driver-video-fglrx.spec
   * xorg-driver-video-nvidia.spec
-  * xorg-driver-video-nvidia-legacy.spec
   * xorg-driver-video-nvidia-legacy2.spec
   * xorg-driver-video-nvidia-legacy3.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:
  
  {{{
- ./builder -d ti -r --kernel vanilla atl2.spec:auto-ti-atl2-2_0_4-3
+ ./builder -d ti -r --kernel bare-vserver atl2.spec:auto-ti-atl2-2_0_4-3
  }}}
  
  Keep in mind that each of mentioned packages must be succesfully built for 
each and every kernel, including pae ones. Thats lot of rebuilding. Also be 
sure that %{version}-%{release} of kernel packages matches 
%{version}-%{release} of userspace part.
_______________________________________________
pld-cvs-commit mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit

Reply via email to