Experimental Physics and
Industrial Control System

[email protected] (Marty Kraimer) · Fri, 8 Dec 1995 10:45:17 -0600

Proposed refinement of procedures for EPICS Software Distribution.

Please comment if you have suggestions for improvement.
This information will be added to the document
"Distributed Development, Distribution, and Support"
when we have agreed on the following.

The goal is to distribute all EPICS software via the WWW.

For each release of EPICS the following will be available at APS
via the WWW. I am assuming that files containing epics source files
can be password protected.

APS HOME PAGE
  APS Overview
    EPICS Information
      Software Distribution (This replaces Statically Linked Extensions)

At this point a new page comes up containing:

EPICS Software Distribution

Base
  Release 3.12.2
    README
    ReleaseNotesBase
    baseUnbuilt.tar.Z
    patchesBase (NOTE: details on separate page)
	README
	<fix1>.c
	<fix2>.c
		...
  Release <perfection>
    <like Release 3.12.2>
Extensions
  Release 3.12.2
    README
    ReleaseNotesExtensions
    extensionsUnbuilt.tar.Z
    patchesExtensions (NOTE: details on separate page)
	README
	<fix1>.c
	<fix2>.c
		...
Platform Specific
  solaris (NOTE: Details on a separate page)
    Release 3.12.2
	README
	basePreBuilt.tar.Z
	extensionsPreBuild.tar.Z  Sources + Binaries
	patchesBase
		README
		<fix1>.c
		<fix2>.c
		...
	patchesExtensions
		README
		<fix1>.c
		<fix2>.c
		...
	staticBuiltExtensions
		alh.Z
			...
  sun4 (NOTE: Details on a separate page)
	<like solaris>
  HPUX
  ...

APS Beamline Users (NOTE: Details on a separate page)
  <Whatever they want>
GEMINI Users (NOTE: Details on a separate page)
....

NOTES:

The platform dependent portion of the tree will be maintained by
the Platform Developer. Each Platform developer can decide if
he/she wants to maintain this subtree locally, i.e. APS
only has a URL referencing the developers site,  or on the APS epics site.

The user specific portions, e.g. "APS Beamline Users" are managed by
associated users.  The APS WWW merely has a URL refering to the user site.

APS will maintain the Base and Extensions portion of the tree.

QAPS is also willing to initially populate the solaris and sun4
specific portions for new releases (our users need them!!) but
will rely on the associated Platform Developers to handle problems.
For sun4 we will not be able to accept responsibility for sun4
once we have completely converted APS/ASD to solaris.

Do we have to have more unbundling of extensions?
The problem is that from the point of view of management the answer
is yes but from the point of view of users more unbundling is a pain.

Marty Kraimer

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System