Hello,
 
Although these dependencies will go away in the next release, CASTOR-client and CSEC are needed by the LFC-client.
 
So, if you want to be able to use the LFC-client, CASTOR-client should not be removed...
But, as I said, this will go away in the next release.

Cheers, Sophie.
 
________________________________

From: LHC Computer Grid - Rollout on behalf of Markus Schulz
Sent: Fri 5/13/2005 10:02 AM
To: [log in to unmask]
Subject: Re: [LCG-ROLLOUT] Do you know what's on your Nodes? who said spyware?



Dear Fabien,
as you mentioned. not all RPMs that are in the distribution are needed 
at the same time.
The middleware can be setup in several different ways and the sites 
have different solutions to choose (like MPICH support or not,
deploying Tank&Spark or not).
To limit the complexity of our task of providing RPM list we merge all 
these options into a superset. This clearly comes at the cost of some
wasted space.
The reason why we have so many individual RPMs in the edg/vdt/lcg 
categories has  historic roots based on the fact that edg,  lcg, and 
vdt are
assembles of software of different origin. Again for practical reasons 
these components have been packaged individually.

The third category of components are those that the middleware has 
dependencies on. The  number of these packages is large and this
haas been identified as a major problem in the past. To minimize the 
external reference was one of the requirements from the deployment team
given to the gLite developers.

To what level do you expect a documentation of the individual packages?
The sources are available and the comprehensive documentation produced 
by the teams that produced the software.

The RPMs themselves contain information about what is in and you can 
access this information either via one of the many
graphical package browsers (like Synaptic), or "rpm  -q -i 
package_name".

The fourth category are packages that are entire useless on a specific 
node type and made it into the list by mistake. For some we have open 
bugs
in the bug tracker.

   markus

On May 12, 2005, at 6:19 PM, Fabien Wernli wrote:

> Hi,
>
> We're in the process of upgrading our WNs to 2_4_0.
> After struggling with the usual local dependency problems and lcg-WN 
> meta-package,
> I have spent some time on checking what's changed since 2_3_1 and more
> fundamentally what the heck's being installed on our machines ;o)
>
> At the time being we have the following dependencies on lcg-WN as of 
> version 2.4.0-sl3
> (please read on and sorry for the flood, which is part of my point 
> BTW):
>
> | edg-profile >= 2.0.8-1
> | lcg-profile >= 1.0.4-1
> | edg-utils-system >= 1.7.0-1
> | edg-mkgridmap >= 2.4.1-1_sl3
> | edg-mkgridmap-conf >= 2.4.1-1_sl3
> | perl-Convert-ASN1 >= 0.18-sl3
> | perl-IO-Socket-SSL >= 0.96-sl3
> | perl-Net_SSLeay >= 1.25-sl3
> | perl-XML-SAX-Base >= 1.04-1
> | perl-ldap >= 0.31-sl3
> | perl-Crypt-SSLeay >= 0.51-1
> | j2sdk
> | log4j >= 1.2.6-1jpp
> | jakarta-commons-logging >= 1.0.2-lcg1_sl3
> | bouncycastle-jdk14 >= 1.19-2
> | jakarta-axis >= 1.1rc2-3
> | commons-cli >= 1.0_beta2_edg-2edg
> | xerces-j1 >= 1.4.4-12jpp
> | xml-commons >= 1.0-0.b2.3jpp_sl3
> | xml-commons-apis >= 1.0-0.b2.3jpp_sl3
> | jug >= 1.0.2_edg-edg2
> | globus-config >= 0.22-1.lcg
> | globus-initialization >= 2.2.4-5
> | edg-allschema-config >= 0.2.1-1
> | edg-gpt-profile >= 1.0.0-1
> | gpt >= VDT1.2.0rh9-1
> | vdt_globus_data_server >= VDT1.2.0rh9-1
> | vdt_globus_essentials >= VDT1.2.0rh9-1
> | vdt_globus_info_client >= VDT1.2.0rh9-1
> | vdt_globus_info_essentials >= VDT1.2.0rh9-1
> | vdt_globus_info_server >= VDT1.2.0rh9-1
> | vdt_globus_rm_client >= VDT1.2.0rh9-1
> | vdt_globus_rm_essentials >= VDT1.2.0rh9-1
> | vdt_globus_rm_server >= VDT1.2.0rh9-1
> | vdt_globus_sdk >= VDT1.2.0rh9-1
> | vdt_globus_jobmanager_condor >= VDT1.2.0rh9-1
> | vdt_globus_jobmanager_lsf >= VDT1.2.0rh9-1
> | vdt_globus_jobmanager_pbs >= VDT1.2.0rh9-1
> | myproxy >= VDT1.2.0rh9-1
> | myproxy-config >= 1.1.8-13.edg1
> | voms-api_gcc3_2_2 >= 1.3.7-2_sl3
> | voms-api-gcc32dbgpthr-_gcc3_2_2 >= 1.3.7-2_sl3
> | voms-client_gcc3_2_2 >= 1.3.7-2_sl3
> | edg-voms-admin-client >= 0.7.6-1_sl3
> | edg-voms-admin-interface >= 0.3.2-3_sl3
> | edg-voms-admin-devel >= 0.7.6-1_sl3
> | gacl >= 0.9.2-1_gcc3_2_2_sl3
> | perl-SOAP-Lite >= 0.55-sl3
> | lcg-voms-alice >= 2.0.0-1
> | lcg-voms-atlas >= 2.0.0-1
> | lcg-voms-cms >= 2.0.0-1
> | lcg-voms-dteam >= 2.0.0-1
> | lcg-voms-lhcb >= 2.0.0-1
> | lcg-vomscert-alice >= 2.0.0-1
> | lcg-vomscert-atlas >= 2.0.0-1
> | lcg-vomscert-cms >= 2.0.0-1
> | lcg-vomscert-dteam >= 2.0.0-1
> | lcg-vomscert-lhcb >= 2.0.0-1
> | edg-java-data-util >= 1.3.22-1_sl3
> | edg-java-security >= 1.5.11-1_sl3
> | edg-java-security-client >= 1.5.11-1_sl3
> | edg-java-security-test >= 1.5.11-1_sl3
> | edg-replica-optimization-interface >= 2.2.0-1_sl3
> | edg-replica-optimization-client >= 2.2.2-1_sl3
> | edg-replica-optimization-test >= 2.2.2-1_sl3
> | edg-replica-optimization-client-c++_gcc3_2_2 >= 2.3.4-1_sl3
> | edg-gsoap-base_gcc3_2_2 >= 1.1.5-1_sl3
> | edg-local-replica-catalog-interface >= 2.2-1_sl3
> | edg-local-replica-catalog-client >= 2.2.9-1_sl3
> | edg-local-replica-catalog-test >= 2.2.9-1_sl3
> | edg-replica-location-client-c++_gcc3_2_2 >= 2.3.2-1_sl3
> | edg-replica-metadata-catalog-interface >= 2.2-1_sl3
> | edg-replica-metadata-catalog-client >= 2.2.9-1_sl3
> | edg-replica-metadata-catalog-test >= 2.2.9-1_sl3
> | edg-replica-metadata-catalog-client-c++_gcc3_2_2 >= 2.3.3-1_sl3
> | CSEC >= 1.1.3-1_sl3
> | LFC-client >= 1.2.6-1sec_sl3
> | CASTOR-client >= 1.7.1.5-1.longname
> | xerces-c >= 1.7.0-sl3
> | edg-replica-manager-interface >= 1.8.0-1_sl3
> | edg-replica-manager >= 1.8.1-1_sl3
> | edg-replica-manager-config >= 1.8.1-1_sl3
> | edg-replica-manager-test >= 1.8.1-1_sl3
> | edg-replica-manager-gridftp-client_gcc3_2_2 >= 1.8.1-1_sl3
> | edg-replica-manager-client-c++_gcc3_2_2 >= 2.3.5-1_sl3
> | CGSI_gSOAP_2.3 >= 1.1.3-2_sl3
> | GFAL-client >= 1.5.7-1_sl3
> | lcg_util >= 1.2.9-1_sl3
> | d-cache-client >= 1.0-76
> | edg-wl-services-common_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-logging-api-c_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-logging-api-cpp_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-logging-api-sh_gcc3_2_2 >= lcg2.1.62-1_sl3
> | ares-devel >= 1.1.1-cel3
> | edg-wl-bypass_gcc3_2_2 >= lcg2.5.3-29_sl3
> | edg-wl-chkpt-api_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-common-api_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-common-api-java_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-common-api-java-interface_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-ui-api-cpp_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-ui-api-java_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-ui-api-java-interface_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-ui-cli_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-ui-config_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-ui-gui_gcc3_2_2 >= lcg2.1.62-1_sl3
> | edg-wl-config_gcc3_2_2 >= lcg2.1.62-1_sl3
> | classads-jar >= 1.1-2
> | cog-jar >= 1.1-1
> | tkinter >= 2.2.3-5
> | boost-g3 >= 1.29.1-05vh_sl3
> | classads-g3 >= 0.9.4-vh7_sl3
> | edg-rgma-base >= 4.0.8-1
> | edg-rgma-api-c >= 4.0.2-1
> | edg-rgma-api-cpp >= 4.0.6-1
> | edg-rgma-api-java >= 4.0.2-1
> | edg-rgma-api-perl >= 4.0.2-1
> | edg-rgma-api-python >= 4.0.5-1
> | edg-rgma-gin >= 4.0.6-1
> | edg-rgma-command-line >= 4.0.5-1
> | edg-rgma-log4cpp >= 4.0.2-0
> | edg-rgma-log4j >= 4.0.2-1
> | edg-rgma-stubs-servlet-java >= 4.0.5-1
> | edg-rgma-system-tests >= 4.0.3-1
> | jas-jar >= 1.0.0-1
> | jxUtil-jar >= 1.0.1-1
> | swig_lcg >= 1.3.19-6.1_sl3
> | edg-essentials-cpp >= 1.1.1-1
> | netlogger-jar >= 1.0.0-1
> | cppunit >= 1.8.0-sl3
> | mm.mysql >= 2.0.14-1edg
> | edg-rgma-apel >= 3.4.42-1
> | lcg-spark-gcc32dbg >= 2.0-1_sl3
> | lcg-tankspark-conf >= 2.0-2_sl3
> | mpich >= 1.2.5-63_sl3
> | edg-gridftp-client >= 1.2.5-1
> | edg-brokerinfo_gcc3_2_2 >= 2.1-5_sl3
> | lcg-ManageSoftware >= 2.0-1
> | lcg-info >= 1.2-1
> | lcg-info-api-ldap >= 2.4-2
> | lcg-user-configuration >= 1.0.4-1_sl3
> | a1_grid_env >= 1.0.0-1
> | lcg-wn-os >= 1.0.0-1_sl3
> | lcg-mon-wn >= 1.0.5-1_sl3
> | lcg-version >= 2.4.0-1
> | lcg-yaim >= 2.4.0-2
> | j2sdk_profile >= 1.4.2_08-sl3
> | rpmlib(VersionedDependencies) <= 3.0.3-1
> | rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> | rpmlib(CompressedFileNames) <= 3.0.4-1
>
> Now not going into details, it appears to me that there is stuff there 
> we
> don't need, -- which is the case BTW for other meta-packages as well --
> like the usual CASTOR-client we remove (we have our own rfio), mpich, 
> swig,
> lots of documentation lots of development tools, not mentioning cryptic
> package names with dubious version "numbers" like ther was in 2_3_1 
> e.g.
> voms-api-gcc32dbgpthr-_gcc3_2_2-1.2.0.14-1_RH7.3.i386.rpm ...
>                                            ^^^^^
>
> Also why does my CE need lcg-tank-gcc32dbg, MySQL-server ... ?
>
> My point is, I would like to know for each node-type what is the 
> purpose of
> each installed package. And don't tell me "it's a test for sysadmins" 
> ;-)
>
> Thanks for taking your time to answer this one, I think it's important 
> for
> all sysadmins installing middleware.
>
>

************************************************************************
*******
Markus Schulz
CERN IT