GC stale description files in vespabase

3 files changed, 0 insertions, 85 deletions

diff --git a/vespabase/desc.services b/vespabase/desc.services
deleted file mode 100644
index b92af60e802..00000000000
--- a/vespabase/desc.services
+++ /dev/null
@@ -1,14 +0,0 @@
-CloudConfig Runtime Environment
-
-The services package contains (via dependencies)
-common runtime cloudconfig components.
-
-The services package adds a set of environment settings that are used by several
-of the control scripts and binaries that use cloud config. The
-current list looks like this:
-
-# set port_configserver_rpc
-# set addr_configserver
-    
-These values allow the other components to locate the configuration
-server, thus enabling them to get their config.
diff --git a/vespabase/desc.vespa_base b/vespabase/desc.vespa_base
deleted file mode 100644
index 965fdaffdbb..00000000000
--- a/vespabase/desc.vespa_base
+++ /dev/null
@@ -1,36 +0,0 @@
-Vespa Runtime Environment
-
-The vespa_base package contains (via dependencies)
-common runtime Vespa components.
-
-Runtime libraries for c++ and java:
-
-    * vespa_gcc3 vespa_gcc_runtime:  C++ runtime
-    * libiconv:                      Iconv shared library.
-
-General utilities:
-
-    * vespa_log: Vespa log handling utilities.
-    * vespa_gdb: A version of gdb that works with the Vespa compiler.
-    * ywget:     Commandline URL-getter.
-
-Required services that will always be present on a vespa node:
-
-    * vespa_configd:      The vespa service starter (config-sentinel).
-    * vespa_config_proxy: Local daemon for communication with the
-                          configuration server.
-    * vespa_logd:         Local daemon for forwarding the vespa.log to the
-                          logserver.
-    * vespa_slobrok:      Service Location Broker used by the messaging layer.
-
-Settings for the runtime environment
-
-Vespa Base adds a set of environment settings that are used by several
-of the control scripts and binaries that are part of Vespa. The
-current list looks like this:
-
-# set port_configserver_rpc 
-# set addr_configserver 
-    
-These values allow the other components to locate the configuration
-server, thus enabling them to get their config.
diff --git a/vespabase/desc.vespa_base_dev b/vespabase/desc.vespa_base_dev
deleted file mode 100644
index 1f05be94257..00000000000
--- a/vespabase/desc.vespa_base_dev
+++ /dev/null
@@ -1,35 +0,0 @@
-Vespa Developer libraries
-
-Vespa Base, in the package vespa_base_dev, contain a set of development
-libraries and utilities for use when developing you vespa service.
-The following is a short list.
-
-Vespa specific libraries:
-
-    * vespa_config_dev: config code generator and include-files and
-      libraries for the basic datatypes. Both for Java and C++.
-    * vespa_log and vespa_log_dev: Log-handling utilities, and log
-      libraries for Java and C++
-    * vespa_document_dev: C++ headers and static library, and Java
-      jar file, for working with Vespa document objects. This is the
-      basic element of the Vespa framework.
-    * vespa_slobrok and vespa_slobrok_dev: The actual Service
-      Location Broker component, as well as C++ headers and libraries
-      for being a slobrok client or server.
-
-Generic libraries:
-
-    * vespa_fastlib and vespa_fastlib_dev: Misc utilities library
-      containing unicode processing and an HTTP server, among other
-      things. Used by some Vespa components for legacy reasons.
-    * vespa_fastos_dev: OS abstraction layer and generic build
-      management utilities.
-    * vespa_fnet_dev: General purpose network library, with an RPC
-      layer. C/C++ headers and libraries.
-    * vespa_vespajlib_dev: Misc utility classes for Java.
-    * vespa_vespalib_dev: Misc utility classes for C++.
-
-Development tools and 3rd party libraries:
-
-    * vespa_boost_dev: Boost headers,
-      prepared for use with the Vespa compiler.