Difference between revisions of "Debian"

From Davical
Jump to navigationJump to search
Line 1: Line 1:
 +
== Installation notes ==
 
Installing on Debian should be fairly straightforward.  The instructions on the [http://rscds.sourceforge.net/installation.php standard installation page] should cover this just fine.
 
Installing on Debian should be fairly straightforward.  The instructions on the [http://rscds.sourceforge.net/installation.php standard installation page] should cover this just fine.
  
 +
* during the creation of the PostgreSQL user, you'll be asked wether the new role should be super-user; it's safe to answer "no".
 +
 +
== Roadmap ==
 
In due course (after Lenny is released) we expect to improve the packaging of RSCDS and upload it directly to Debian.  This won't be done before Lenny's release because it will add a dependency on two packages which are not going to be released as part of Lenny.  
 
In due course (after Lenny is released) we expect to improve the packaging of RSCDS and upload it directly to Debian.  This won't be done before Lenny's release because it will add a dependency on two packages which are not going to be released as part of Lenny.  
 
<ul><li style="list-style-type:none">Sorry, can't make sense of this. How will the package be useful if it's dependent on packages that aren't available? And why can't they be put into the distribution?  
 
<ul><li style="list-style-type:none">Sorry, can't make sense of this. How will the package be useful if it's dependent on packages that aren't available? And why can't they be put into the distribution?  

Revision as of 15:09, 30 April 2009

Installation notes

Installing on Debian should be fairly straightforward. The instructions on the standard installation page should cover this just fine.

  • during the creation of the PostgreSQL user, you'll be asked wether the new role should be super-user; it's safe to answer "no".

Roadmap

In due course (after Lenny is released) we expect to improve the packaging of RSCDS and upload it directly to Debian. This won't be done before Lenny's release because it will add a dependency on two packages which are not going to be released as part of Lenny.

  • Sorry, can't make sense of this. How will the package be useful if it's dependent on packages that aren't available? And why can't they be put into the distribution?
    • It will be dependent on the webapps-common package which the Debian Developer has stated will not be released into Debian until after Etch is released. I will also use dbconfig-common, which I thought was going to suffer the same fate, but it appears that one will be in Etch. I am hopeful that these packages will provide a structure to enable a smarter configuration and upgrade process.

In the mean time the packages are available from a non-standard repository which you can use by adding this apt source to your /etc/apt/sources.list:

deb http://debian.mcmillan.net.nz/debian lenny awm

This repository is signed with the GPG key 0x8f068012 which should be available from the Debian keyring or many other keyservers.