Hi,
This is the 2nd iteration of proposed procedures for distributing EPICS code
via the WWW. The only comments so far have been from Mark Rivers (the version
below includes his suggested changes). Please comment by the end of this week
or else these will be the procedures.
Also I need help. Does anyone know how to make a Network brouser obtain
software via password protected ftp? What is the associated URL and what
brousers accept it? How is binary mode specified? Please answer if you know.
If we cant do this we will have to make people get software via ftp
rather than a brouser.
Here is latest proposal
___________________________________________________________
Proposed refinement of procedures for Platform responsibilities
Please comment if you have suggestions for improvement.
This information will be added to the document
"Distributed Development, Distyribution, and Support"
when we have agreed on 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 (Unix binaries only. User has to build IOC)
patchesBase (Platform specific additions to Base/patchesBase)
README
<fix1>.c
<fix2>.c
...
patchesExtensions (Platform specific additions to Extensions/patchesExt)
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.
APS 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.
What about things like GNU, CVS, and TCL/TK? Should these be made available
via the APS site? Who will maintain these products? What is the complete list?
Do any of them have platform dependent problems?
- Navigate by Date:
- Prev:
EPICS VMS distribution Mark Rivers
- Next:
subscribe Bakul Banerjee
- Index:
1994
<1995>
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
ATTN Platform Developers Marty Kraimer
- Next:
Re: ATTN Platform Developers Steve Lewis
- Index:
1994
<1995>
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|