Yes and no. My rule of thumb has always been to use the packaged version of a
software package unless there's a very good reason not to.
We maintain a local package repository as well (using debarchiver), so if we
need to make a custom version of a Debian/Ubuntu package, we generally make the
change to the debian source package, build it with a new localised version
number, and then upload it to our local repository. For example, our local
version of the blcr stuff:
12:24:13 tjrc@farm3-head2:~$ apt-cache policy blcr-dkms
blcr-dkms:
Installed: 0.8.5-2.1~sanger2
Candidate: 0.8.5-2.1~sanger2
Version table:
*** 0.8.5-2.1~sanger2 0
500 http://debian.internal.sanger.ac.uk/debian-sanger/ precise/main
amd64 Packages
100 /var/lib/dpkg/status
0.8.2-15ubuntu2.1 0
500 http://www.mirrorservice.org/sites/archive.ubuntu.com/ubuntu/
precise-updates/universe amd64 Packages
0.8.2-15ubuntu2 0
500 http://www.mirrorservice.org/sites/archive.ubuntu.com/ubuntu/
precise/universe amd64 Packages
12:24:54 tjrc@farm3-head2:~$
There are other cases where we just build from source separately (generally if
it's something which has to work across multiple Linux versions, and therefore
sits in our /software NFS filesystem). We do this for our centrally supported
R distributions, for example.
Regards,
Tim
From: Jonathan Aquilina
<[email protected]<mailto:[email protected]>>
Date: Friday, 20 May 2016 at 11:34
To: Tim Cutts <[email protected]<mailto:[email protected]>>
Cc: Christopher Samuel <[email protected]<mailto:[email protected]>>,
Beowulf <[email protected]<mailto:[email protected]>>
Subject: Re: [Beowulf] cluster os
Going a bit off track from upgrades here. In a cluster environment with debian
do you spend a fair bit of time compiling anything from source?
_______________________________________________
Beowulf mailing list, [email protected] sponsored by Penguin Computing
To change your subscription (digest mode or unsubscribe) visit
http://www.beowulf.org/mailman/listinfo/beowulf
