Maintaining an installation - Revision history

Hattne: Updated link to PSDM installation instructions.

2014-02-28T23:45:37Z

Updated link to PSDM installation instructions.

← Older revision		Revision as of 23:45, 28 February 2014
Line 1:		Line 1:
	== Keeping up to date with PSDM releases==		== Keeping up to date with PSDM releases==

	<!-- XXX Separate installation and maintenance instructions are provided by the PSDM project at [https://confluence.slac.stanford.edu/display/~~PCDS~~/~~PSDM+software~~+~~distribution~~ PSDM software distribution]. XXX Also missing bit on how to update cctbx for non-developers. -->		<!-- XXX Separate installation and maintenance instructions are provided by the PSDM project at [https://confluence.slac.stanford.edu/display/PSDM/Software+Distribution PSDM software distribution]. XXX Also missing bit on how to update cctbx for non-developers. -->

	Since the ''cctbx.xfel'' modules do not critically depend on any particular version of ''pyana'', it is generally safe to closely track the latest version of the PSDM software distribution. To upgrade to the current PSDM release,		Since the ''cctbx.xfel'' modules do not critically depend on any particular version of ''pyana'', it is generally safe to closely track the latest version of the PSDM software distribution. To upgrade to the current PSDM release,

Hattne: Noted missing bits.

2014-02-14T00:47:41Z

Noted missing bits.

← Older revision		Revision as of 00:47, 14 February 2014
Line 1:		Line 1:
	== Keeping up to date with PSDM releases==		== Keeping up to date with PSDM releases==

			<!-- XXX Separate installation and maintenance instructions are provided by the PSDM project at [https://confluence.slac.stanford.edu/display/PCDS/PSDM+software+distribution PSDM software distribution]. XXX Also missing bit on how to update cctbx for non-developers. -->

	Since the ''cctbx.xfel'' modules do not critically depend on any particular version of ''pyana'', it is generally safe to closely track the latest version of the PSDM software distribution. To upgrade to the current PSDM release,		Since the ''cctbx.xfel'' modules do not critically depend on any particular version of ''pyana'', it is generally safe to closely track the latest version of the PSDM software distribution. To upgrade to the current PSDM release,
Line 8:		Line 10:
	$ scons		$ scons
	It is possible to manually edit <code><b><i>/path/to/test/release</i></b>/.sit_release</code> to contain <code>ana-current</code> instead of a particular version number. This ensures that the latest version of the PSDM software distribution is used during each session.		It is possible to manually edit <code><b><i>/path/to/test/release</i></b>/.sit_release</code> to contain <code>ana-current</code> instead of a particular version number. This ensures that the latest version of the PSDM software distribution is used during each session.


	== Keeping a developer installation up to date ==		== Keeping a developer installation up to date ==

Hattne: Unified maintenance for regular users and developers.i

2014-02-07T10:56:23Z

Unified maintenance for regular users and developers.i

← Older revision		Revision as of 10:56, 7 February 2014
Line 8:		Line 8:
	$ scons		$ scons
	It is possible to manually edit <code><b><i>/path/to/test/release</i></b>/.sit_release</code> to contain <code>ana-current</code> instead of a particular version number. This ensures that the latest version of the PSDM software distribution is used during each session.		It is possible to manually edit <code><b><i>/path/to/test/release</i></b>/.sit_release</code> to contain <code>ana-current</code> instead of a particular version number. This ensures that the latest version of the PSDM software distribution is used during each session.


			== Keeping a developer installation up to date ==

			Given the rapid development of the ''PHENIX'' suite, it is recommended to update the sources and rebuild often. Certain changes may require the configure command (or <code>libtbx.refresh</code>) to be rerun.
			$ cd <b><i>/path/to/cctbx/sources</i></b>
			$ ./allsvn update
			$ cd <b><i>/path/to/cctbx/build</i></b>
			$ make
			<!-- XXX How often should one do something about the hot tarballs (i.e. annlib_hot.tar.gz, boost_hot.tar.gz, and scons_hot.tar.gz)? XXX See also Nick’s note at the end of document about the New framework for specifying crystal targets. -->

Hattne: Migrated text from PSDM page.

2014-02-07T08:31:47Z

Migrated text from PSDM page.

New page

== Keeping up to date with PSDM releases==

Since the ''cctbx.xfel'' modules do not critically depend on any particular version of ''pyana'', it is generally safe to closely track the latest version of the PSDM software distribution. To upgrade to the current PSDM release,
$ cd /path/to/test/release
$ relupgrade ana-current
where <code>/path/to/test/release</code> must be substituted for path of the test release. The ''cctbx.xfel'' modules should then be rebuilt using
$ scons -c
$ scons
It is possible to manually edit <code>/path/to/test/release/.sit_release</code> to contain <code>ana-current</code> instead of a particular version number. This ensures that the latest version of the PSDM software distribution is used during each session.