Difference between revisions of "User:Dennisvd@nikhef.nl/UserSpacePackageManagement"

From PDP/Grid Wiki
Jump to navigationJump to search
Line 13: Line 13:
 
# bootstrap it for the local system. This creates a directory called 'work'.
 
# bootstrap it for the local system. This creates a directory called 'work'.
 
#:./bootstrap --prefix /data/esia/pvier/pkg --unprivileged
 
#:./bootstrap --prefix /data/esia/pvier/pkg --unprivileged
 +
#:(I should try this on a minimalist system to see which build dependencies this brings).

Revision as of 16:10, 21 May 2010

Managing software packages on the Grid is complicated, because there is no central control over the setup of the operating environment across clusters. Even in a relatively small, tightly coordinated collection of clusters such as BiG Grid, the offering of packages is not tailored to the user's needs.

There has always been the option for users (or rather, VOs) to place their own software in special locations on a per-cluster basis. This is a low-level fallback, basically offering just file system access and nothing else. To do proper package management in these so-called VO software areas is something that needs to be looked at.

There are various possibilities, but the one explored here concerns pkgsrc by NetBSD. It is a widely available open-source system that fetches and builds software from source whenever needed.

Installation steps

  1. download pkgsrc (choose the most recent quarterly release; approximate size is 30MB)
  2. Let's assume the the VO software area is /data/esia/pvier. Unpack the pkgsrc distribution there.
    tar xfz pkgsrc.tar.gz
    cd pkgsrc
  3. bootstrap it for the local system. This creates a directory called 'work'.
    ./bootstrap --prefix /data/esia/pvier/pkg --unprivileged
    (I should try this on a minimalist system to see which build dependencies this brings).