Differences

This shows you the differences between two versions of the page.

--- titanium [2010-03-27 17:06]
hawk
+++ titanium [2010-08-28 23:21]
hawk
@@ Line 1: / Line 1: @@
-====== About PLD Titanium ======
-Titanium is an unofficial version of PLD created and managed by [[:hawk|Hawk]]. It was based on PLD 2.0 (Ac) and provides more up to date software from PLD 3.0 (Th). It is completly separate version of PLD with architectures limited to 586, 686 and x86_64. Titanium uses "always in developement" distribution model thus some big upgrades are to be expected from time to time (notifications will be available on Hawks blog). Main goal for Titanium is to provide stable and working system.
@@ Line 11: / Line 6: @@
-===== PLD Titanium features =====
+===== About PLD Titanium =====
-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.
+Titanium is an unofficial version of PLD created and managed by [[:hawk|Hawk]]. It is completly separate version of PLD with architectures limited to 586, 686 and x86_64. Main goal for Titanium is to provide stable and working system.
-Available package trees:
-|**Tree**|**Directory on FTP**|**Description**|
+===== Stable version =====
-|Stable|PLD|Current stable version of system also referred as "Main".|
+Stable version is dedicated for all systems where stability is more important than having newest available versions of software packages. It is based on snapshots created from development version. Such snapshot will get only minor updates and bug/security fixes to provide reasonable level of stability and predictability. However once new snapshot is released it may incorporate some big updates which may require adminitrator intervention to get things going. Appropriate information will always be published on pld-titanium [[:MailingLists|mailing list]] at least one week before new version is released.
-|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!|
+Current stable version: 2010.01
-|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:
+Available kernel versions:
@@ Line 36: / Line 30: @@
   * gcc 4.4.x
   * KDE 4.4.x
-  * Gnome 2.28.x
+  * Gnome 2.30.x
   * XFCE 4.4.3
   * Open''''Office.org 3.2.x
+Available package trees:
-===== Distribution status =====
+|**Tree**|**Directory on FTP**|**Description**|
-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]].
+|stable|PLD|Current stable version of system.|
+|pre-stable|test|Packages scheduled to be moved to stable tree. They should work ok, but remember they aren't stable yet. Use with care as they may still contain bugs or even brake 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.|
+===== Devel version =====
+Development version as name suggests is used for developing next version of stable snapshot. Since it by definition may contain unfinished or untested packages it is **not recommended** to use it on any production systems.
+To switch from stable to development version:
+  * disable stable sources in your poldek configuration
+  * enable devel sources in your poldek configuration
+  * perform poldek --upgrade-dist
+Current development version will become stable snapshot 2010.02. Planned release date: end of 2010.
+Planned version changes:
+  * kernels 2.6.34.x or 2.6.36.x (preferable 2.6.36.x)
+  * OpenSSL 1.0
+  * PHP 5.3.x
+  * XServer 1.9.x
+Available package trees:
+|**Tree**|**Directory on FTP**|**Description**|
+|devel|PLD|Current development version of system.|
+|pre-devel|test|Test packages which may or may not be moved to devel tree.|
+===== Installation =====
 Installation is possible using [[http://cri.pld-linux.org/|CRI]] or manually using [[ftp://ftp1.pld-linux.org/people/hawk/cri/chroots/|CRI chroots]].
@@ Line 49: / Line 72: @@
 ===== Distribution future =====
-Packages needed and used by developers will be maintained however some rarely used stuff requested by users will not get any attention. We (PLD Titanium developers) simply don't have enough time resources to maintain thousands of packages. Keep that in mind when choosing Titanium.
+Packages needed and used by developers will be maintained however some rarely used stuff requested by users will not get any attention. We (PLD Titanium developers) simply don't have enough time and resources to maintain thousands of packages. Keep that in mind when choosing Titanium.
 We will do our best to:
@@ Line 55: / Line 78: @@
   * maintain core packages (security fixes, updates)
-  * don't allow broken dependencies to emerge in package tree
+  * don't allow broken dependencies to emerge in stable version
   * 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)
@@ Line 63: / Line 86: @@
 //Q: Why you have created PLD Titanium?//\\ 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?//\\ 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: 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?//\\ A: PLD Titanium uses official PLD CVS so all changes/updates made in official PLD are automatically available for Titanium and few PLD developers are taking care of building packages for Titanium.
-//Q: So if you are using same stuff as PLD then what is the difference between Th and Titanium?//\\ 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: So if you are using same stuff as PLD then what is the difference between Th and Titanium?//\\ A: The difference is mainly in management. I have my own idea how distro should be managed. Titanium also has separate stable and develeopment version.
-//Q: If I understand correctly, if you will need some change in Titanium you will simply do it no matter what it may break?//\\ 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?//\\ A: Yes. As long as you don't use test package tree od development version you shouldn't have any special problems. You may encounter some problems when new stable snapshot is released because it may incorporate some big changes. However when updating any other Linux distribution between major versions you may encounter same or even worse problems too.
-//Q: Is it safe to use PLD Titanium?//\\ 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 your own packages with your own configuration using PLD CVS.
+//Q: Is there a risk that you will abandon PLD Titanium some day?//\\ 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 any PLD developer may take it over and continue my work.
-//Q: Is there a risk that you will abandon PLD Titanium some day?//\\ 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.
-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.
@@ Line 84: / Line 105: @@
 ===== Notes from Hawk for PLD developers =====
-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.
+If you are PLD developer and you want STBR permission for stable or devel version, let me know. Also please read few rules below before doing actual developement in PLD CVS or sending build requests.
@@ Line 98: / Line 119: @@
     * there is no stable version yet
-    I decide what goes into distribution and what doesn't. That includes patches and default values of bconds. In other words: I'm release manager and that can't be changed unless I'll say otherwise or resign from maintaining PLD Titanium.
+    I as release manager decide what goes into distribution and what doesn't. That includes patches and default values of bconds. Discussions are welcome at pld-titanium mailing list.
-    If you are upgrading something you are the one who must care for all dependant packages to be upgraded/rebuilt. If you know you won't finish it, don't start upgrade at all.
+    If you are upgrading something you are the one who must care for all dependant packages to be upgraded/rebuilt. If you know you won't finish it, don't start upgrade at all or find someone who fill finish it for you.
-    If you are about to update some package which after upgrade will not work without manual intervention, ask me first.
+    If you are about to update some package which after upgrade will not work without manual intervention, ask on pld-titanium mailing list first.
     Don't sent upgrade builds if some architecture fails. If you already sent one and don't know how to fix broken arch, let me know ASAP.
     Use test builds for testing if something compiles/works. Test builds are available (with poldek indexes) in .test-builds folder on FTP however they're kept only for two weeks.
@@ Line 106: / Line 127: @@
     Things currently not allowed in PLD Titanium:
     * enabling vda patch in postfix (breaks default postfix behaviour with virtuals)
-    * upgrading db from 4.5 to newer ones (db >=4.6 causes severe problems with rpm)
+    * upgrading db from 4.5 to newer ones (db >=4.6 was causing severe problems with rpm)
-    * building compat-gcc-34.spec (if you really need gcc 3.4.x please work on gcc3.4.spec)
-    * upgrading libxcb to version > 1.1.90.1
-    * upgrading udev to version > 124
     * upgrading syslog-ng to version > 2.0.x
+==== Maintaining stable version ====
+  - Minor updates/fixes may be sent to builders without prior notice.
+  - Major version changes are allowed if you'll guarantee they'll work and won't brake anything in current installations. If in doubt, ask on pld-titanium mailing list.
+  - Only working / tested packages are allowed. Test before sending to builders. If for some reason packages fails, let me know ASAP.
+  - Build requests are sent using "./make-request -d ti".
+==== Maintaining devel version ====
+  - Don't STBR  stuff newer than versions proposed for next snapshot. Check pld-titanium mailing list for snapshot info.
+  - If you don't agree with pt. 1 and really want something included in next snapshot feel free to "convert" other developers on pld-titanium mailing list.
+  - Build requests are sent using "./make-request -d ti-dev".
 ==== Building kernel stuff ====
-Following specs:branches are used to build kernels for PLD Titanium:
+Following specs:branches are used to build kernels for PLD Titanium Stable:
-  * kernel.spec:LINUX_2_6_27
+  * kernel.spec:LINUX_2_6_32
   * kernel-vanilla.spec:Titanium
   * kernel-bare-vserver.spec:Titanium
@@ Line 137: / Line 170: @@
   * Virtual''''Box.spec
-  * atl2.spec (only for 2.6.27.x kernels)
   * dahdi-linux.spec
   * e1000.spec
@@ Line 146: / Line 178: @@
   * lirc.spec
   * madwifi-ng.spec
-  * sk98lin.spec
   * svgalib.spec
-  * xorg-driver-video-fglrx.spec
+  * xorg-driver-video-nvidia.spec:STABLE
-  * xorg-driver-video-nvidia.spec
   * xorg-driver-video-nvidia-legacy2.spec
-  * xorg-driver-video-nvidia-legacy3.spec
+  * xorg-driver-video-nvidia-legacy3.spec:STABLE
 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:
-<file>./builder -d ti -r --kernel bare-vserver atl2.spec:auto-ti-atl2-2_0_4-3
+<file>./builder -d ti -r --kernel bare-vserver e1000.spec:auto-ti-e1000-8_0_19-11
 </file>
 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 Linux Distribution

User Tools

Site Tools

Differences

Page Tools