This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
th [2009-02-26 14:13] pawelz Removed warning (it is no longer in early stage of development); added note that Th is stable. |
th [2009-05-29 12:23] glen |
||
---|---|---|---|
Line 10: | Line 10: | ||
===== Current status ===== | ===== Current status ===== | ||
- | PLD th is stable, in endless development. No releasea are planned, main repository is constantly updated, but you can consider main th repository as stable distribution. | + | 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. |
Line 27: | Line 27: | ||
==== Separate noarch target ==== | ==== 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). | 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). | ||
+ | |||
+ | |||
+ | |||
+ | ==== Separate debuginfo ==== | ||
+ | In PLD Th introduces debuginfo packages (detached debug info for gdb and friends). In Th all package debuginfo are kept under paths corresponding to their target architectures as ''debuginfo''. This allows smaller poldek indexes meaning poldek likely works faster and perhaps happier mirror maintainers. See [[http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2009-April/020948.html|this]] mailing list post to see how it all started. | ||
==== Directory structure ==== | ==== 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). | + | 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 The "ready" tree is known place as for RM to push packages to main tree, you can consider packages being in ready soon to be in "PLD" tree. |