tarball

Examples of tarball in the following topics:

• Introduction to Testing and Releasing

  • Once the source tarball is produced from the stabilized release branch, the public part of the release process begins.
  • But before the tarball is made available to the world at large, it should be tested and approved by some minimum number of developers, usually three or more.
  • Approval is not simply a matter of inspecting the release for obvious flaws; ideally, the developers download the tarball, build and install it onto a clean system, run the regression test suite (see the section called "Automated testing") in Managing Volunteers, and do some manual testing.
  • Assuming it passes these checks, as well as any other release checklist criteria the project may have, the developers then digitally sign the tarball using GnuPG (gnupg.org), PGP (pgpi.org), or some other program capable of producing PGP-compatible signatures.
  • The more developers sign, the more testing the release undergoes, and also the greater the likelihood that a security-conscious user can find a digital trust path from herself to the tarball.

• Format

  • Producing compressed tar files (or tarballs) is pretty easy.

• Announcing Releases

  • Whenever you give the URL to the downloadable release tarball, make sure to also give the MD5/SHA1 checksums and pointers to the digital signatures file.

• Petroleum Biodegradation

  • Oil tarballs are biodegraded slowly by species from the genera Chromobacterium, Micrococcus, Bacillus, Pseudomonas, Candida, Saccharomyces and others.

• Name and Layout

  • The release—that is, the precise entity referred to when someone says "Scanley 2.5.0"—is the tree created by unpacking a zip file or tarball.
  • The important thing is that the directory created by unpacking the tarball use the same capitalization.