This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
th [2009-02-26 14:18] pawelz typo |
th [2012-09-16 19:55] glen relative link |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | |||
- | |||
- | ====== Info about PLD 3.0 (Th) ====== | ||
- | |||
- | |||
- | ===== Release Manager ===== | ||
- | Arkadiusz Miśkiewicz (arekm at pld linux org) is the current RM. | ||
- | |||
- | |||
- | |||
- | ===== Current status ===== | ||
- | PLD th is stable, in endless development. No releases are planned, main repository is constantly updated, but you can consider main th repository as stable distribution. | ||
- | |||
- | |||
- | |||
- | ==== Supported architectures ==== | ||
- | Development of Th focuses on the following architectures: | ||
- | |||
- | |||
- | * generic x86-64 | ||
- | * x86 (targets: i486, i686, athlon) | ||
- | * PowerPC | ||
- | Support for Alpha, SPARC and i386 wasn't completely dropped, but those architectures will not be part of mainstream development. Additional information will be available at a later date. | ||
- | |||
- | |||
- | |||
- | ==== Separate noarch target ==== | ||
- | In PLD 1.0 and PLD 2.0 noarch RPMs were placed alongside architecture specific packages. This changed in Th and now all packages are kept under paths corresponding to their target architectures (please see the next paragraph to see how to construct such a path). | ||
- | |||
- | |||
- | |||
- | ==== Directory structure ==== | ||
- | In Th, RPMs can always be found under ''th/$treename/$architecture/RPMS/'' directory. Currently "PLD" and "test" trees will be used (most users will probably want to stay away from the latter) and "upgrades-*" trees **might** be used after Th's official release. Do note, that the "ready" tree known from PLD 2.0 will **not** be used in any way that would make it usable to users (assuming it will be used at all). | ||
- | |||
- | |||
- | |||
- | ==== Packages ==== | ||
- | RPM packages are compressed using LZMA, which results in both substantially smaller file sizes and faster decompression. | ||
- | |||