Eliminate all references to apt.conf

[dak.git] / docs / README.first

diff --git a/docs/README.first b/docs/README.first
index 86cb73cdfb03e9d0125a00d9fb43578a82a66ea3..44872bccf982f438c750ba7ac277df5a4d66524e 100644 (file)
--- a/docs/README.first
+++ b/docs/README.first
@@ -5,7 +5,7 @@ o Please be careful: dak sends out lots of emails and if not
   configured properly will happily send them to lots of people who
   probably didn't want those emails.
 
   configured properly will happily send them to lots of people who
   probably didn't want those emails.
 

-o Don't use the debian dak.conf, apt.conf, cron.* etc. as starting
+o Don't use the debian dak.conf, cron.* etc. as starting

   points for your own configuration files, they're highly Debian
   specific.  Start from scratch and refer to the security.debian.org
   config files (-security) as they're a better example for a private
   points for your own configuration files, they're highly Debian
   specific.  Start from scratch and refer to the security.debian.org
   config files (-security) as they're a better example for a private


@@ -46,7 +46,6 @@ o Information display:
 Generic and useful, but only for those with existing archives
 -------------------------------------------------------------
 
 Generic and useful, but only for those with existing archives
 -------------------------------------------------------------
 

-o dak poolize - migrates packages from legacy locations to the pool

 o dak init-archive - initializes a projectb database from an exisiting archive
 
 Generic but not overly useful (in normal use)
 o dak init-archive - initializes a projectb database from an exisiting archive
 
 Generic but not overly useful (in normal use)


@@ -74,9 +73,6 @@ Mostly Debian(.org) specific
 ----------------------------
 
 o dak security-install - wrapper for Debian security team
 ----------------------------
 
 o dak security-install - wrapper for Debian security team

-o dak clean-proposed-updates - removes obsolete .changes files from proposed-updates
-o dak check-proposed-updates - basic dependency checking for proposed-updates
-o dak reject-proposed-updates - manually reject packages from proposed-updates

 o dak import-ldap-fingerprints - syncs fingerprint and uid information with a debian.org LDAP DB
 
 Very Incomplete or otherwise not generally useful
 o dak import-ldap-fingerprints - syncs fingerprint and uid information with a debian.org LDAP DB
 
 Very Incomplete or otherwise not generally useful


@@ -91,22 +87,20 @@ Scripts invoked by other scripts
 --------------------------------
 
 o dak examine-package - invoked by 'dak process-new' to "check" NEW packages
 --------------------------------
 
 o dak examine-package - invoked by 'dak process-new' to "check" NEW packages

-o dak symlink-dists - invoked by 'dak poolize' to determine packages still in legacy locations

 
                        How do I get started?
                        =====================
 
 [Very incomplete - FIXME]
 
 
                        How do I get started?
                        =====================
 
 [Very incomplete - FIXME]
 

-o Write your own dak.conf and apt.conf files.  dak looks for those
-  config files in /etc/dak/.  /etc/dak/dak.conf can define
-  alternative configuration files with Config::host::DakConfig and
-  Config::host::AptConfig (where "host" is the fully qualified domain
-  name of your machine).
+o Write your own dak.conf file.  dak looks for this
+  config file in /etc/dak/.  /etc/dak/dak.conf can define an
+  alternative configuration file with Config::host::DakConfig
+  (where "host" is the fully qualified domain name of your machine).

 o Create a PostgreSQL database on the host given in dak.conf's DB::Host
   with the name specified in DB::Name.
 o Run 'dak init-dirs': this will create all directories which are specified in
 o Create a PostgreSQL database on the host given in dak.conf's DB::Host
   with the name specified in DB::Name.
 o Run 'dak init-dirs': this will create all directories which are specified in

-  dak.conf and apt.conf.
+  dak.conf:

 o If you have an existing archive:
    * Run 'dak init-archive'
   otherwise:
 o If you have an existing archive:
    * Run 'dak init-archive'
   otherwise:


@@ -117,7 +111,7 @@ o If you have an existing archive:
    * Create the following groups in postgres: ftpmaster ftpteam ftptrainee
    * Run 'dak update-db' to upgrade the database schema.
    * Run 'dak init-db': it will populate your database with the values from
    * Create the following groups in postgres: ftpmaster ftpteam ftptrainee
    * Run 'dak update-db' to upgrade the database schema.
    * Run 'dak init-db': it will populate your database with the values from

-     dak.conf and apt.conf.
+     dak.conf

    * Run 'psql <DB::Name> < add_constraints.sql'.
 o Copy all templates from the "templates" directory to to the directory
   specified in Dir::Templates, and adapt them to your distribution.
    * Run 'psql <DB::Name> < add_constraints.sql'.
 o Copy all templates from the "templates" directory to to the directory
   specified in Dir::Templates, and adapt them to your distribution.