PLDWWW: ThInfo

[glen]

Author: glen   Date: Fri May 29 10:23:20 2009 GMT
Module: PLDWWW   URL: http://www.pld-linux.org/ThInfo?action=diff&rev2=17&rev1=16
---- Log message:


---- Page affected: ThInfo

---- Diffs:

================================================================
  
  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 ===
  
- 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.
  
  === Packages ===