TODO List

This TODO list is automatically generated from the <todo> directives in other documents.

• General Concepts
  • The Basics of Autotools

    • Todo

      This is too long for General Concepts. It needs to be split up and moved somewhere, either to a top-level of its own or into Appendices.

      
      

    • Todo

      Stuff about libtool, libtoolize, elibtoolize, libtool.eclass. Which I know almost nothing about... Yay!

      
      
  • Distributed and Parallel Building

    • Todo

      Write this.

      
      
  • Emerge and Ebuild Relationships

    • Todo

      http://dev.gentoo.org/~g2boojum/portage.html

      
      
  • Linguas

    • Todo

      Write this. From vapier: "used to specify languages users wish to have support for. USE=nls covers generally natural language support, but LINGUAS covers specific languages (see the games-rpg/nwn for example). the variable is expanded for USE access in ebuilds. LINGUAS=de would automatically add 'linguas_de' to USE." We also need strip-linguas examples.

      
      
  • Position Independent Code

    • Todo

      policy. http://www.gentoo.org/proj/en/hardened/pic-internals.xml has some technical details.

      
      
  • Privileges

    • Todo

      general privs stuff, include stuff on setuid/setgid and sticky since a lot of people seem to be confused about those... Also notes on the portage user and group issues, and what we use for root:root to make *bsd work.

      
      
• Ebuild Writing
  • Ebuild Functions
    • src_unpack
      • Arch Sources

        • Todo

          Anyone want to write this? You can probably mostly copy the CVS Sources and Subversion Sources chapters.

          
          
      • Debian Sources

        • Todo

          from vapier: we dont have to 'handle' these because all debian packages have a source tarball ... the .deb format is pretty simple though, it's managed by the 'ar' utility from binutils. you can unpack a .deb by simply doing ar x blah.deb ... this will give you three files: debian-binary: plain text file which just contains version number of the .deb format control.tar.gz: a few files which control installing/verifying of package data.tar.gz: all the compiled files ... you could just extract it to /

          
          
• Profiles
  • Profiles profiles.desc File

    • Todo

      Find someone who knows exactly what this file's really used for with current portage versions and what is and isn't allowed.

      
      
  • Profiles updates/ Directory

    • Todo

      move and slotmove

      
      
• Tasks Reference
  • Perl Modules

    • Todo

      write me. see thread on -dev.

      
      
• Eclass Reference
  • cvs.eclass Reference

    • Todo

      Needs to be written

      
      
• Tools Reference
  • bash -- Standard Shell

    • Todo

      tables of bash metachars

      
      

    • Todo

      table of extra bash goodies

      
      
  • sed -- Stream Editor

    • Todo

      write this

      
      
• Appendices
  • Editor Configuration

    • Todo

      from vapier: add a section for nano ... users just have to copy /etc/nanorc to ~/.nanorc and uncomment the sections for ebuilds

      
      
  • Common Problems

    • Todo

      from vapier: TEXTREL's ... binary files which contain text relocations ... see 'prepstrip' for a full description unsafe files ... basically files that are setid and writable by Other users i've added the following QA checks to portage HEAD (no idea when they'll hit a release): Insecure RUNPATHs ... binary files which have RUNPATH's encoded in them which are in +t directories Executable stacks ... binary files whose stack is marked with +x ... will bomb on amd64 for example

      
      

    • Todo

      write me