Back to SPI build and install procedures

Installing a new external software on AFS

External software


  • Who: Yannick Patois
  • How: Using spi_build_external tool
  • When: On requests.

Precisions regarding CVS tagging tracability

  • Fist update and test the XML based configuration and build information (see SpiUpdateXMLConfigInfo?) in a test area.
  • Once it is ready, tag the spi_buil_external package with a new tag named sbe-yyyymmdd-n where yyyymmdd is the current date, and n an incremental number starting at 1.
    cvs tag sbe-yyyymmdd-n
  • Then cvs checkout this release under that tag (for pacman installation, this will be under /afs/ ).
    cvs update -Pd -r sbe-yyyymmdd-n
  • The install script writes the currently used tag in the log file.

Precisions on AFS volume management

As most AFS volumes are now read-only, the installation procedure is a bit more complex on that side.

Creating new volume

  • create the new volume and mount in final place:
    ~pfeiffer/public/scripts/ --pack < package > --vers < version >

  • shrink the volume (to 10% more than actually used)
    afs_admin set_quota /afs/ xxxxx

IMPORTANT: Fill the table at ReplicateAFSVolumes.

Please see ReplicateAFSVolumes for a complete description.


  • None.

-- YannickPatois - 03 Feb 2005

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2005-06-16 - YannickPatois
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    SPI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback