ITP: lumaqq -- Open source QQ clone

Package: wnpp Severity: wishlist * Package name: lumaqq Version : 0.2+20041226 Upstream Author : Ma Ruojie <[EMAIL PROTECTED]> * URL : http://lumaqq.linuxsir.org * License : GPL Description : Open source QQ clone QQ is a instant messenging client using QQ

ITP: libshutter-java -- general QQ-like UI widget based on Java and SWT

Package: wnpp Severity: wishlist * Package name: libshutter-java Version : 0.2+20041226 Upstream Author : Ma Ruojie <[EMAIL PROTECTED]> * URL : http://lumaqq.linuxsir.org * License : GPL Description : general QQ-like UI widget based on Java and SWT Shutte

ITP: libzeus-java -- Open source Java-to-XML Data Binding tool

Package: wnpp Severity: wishlist * Package name: libzeus-java Version : 3.5b Upstream Author : Enhydra Java Application Server Project (http://www.enhydra.org/) * URL : http://zeus.objectweb.org/index.html * License : Enhydra Public License Version 1.1 Descri

ITP: libbase64-java -- Java Base64 encoder and decoder

Package: wnpp Severity: wishlist * Package name: libbase64-java Version : 1.0 Upstream Author : Kevin Kelley <[EMAIL PROTECTED]> * URL : http://jade.tilab.com/ * License : GPL Description : Java Base64 encoder and decoder The package contains simple encod

Re: disabling services: update-rc.d vs. /etc/default/

On Tue, 2004-12-28 at 16:18 +0100, martin f krafft wrote: > also sprach Tilman Koschnick <[EMAIL PROTECTED]> [2004.12.28.1453 +0100]: > > Pro /etc/default/: > > - There is one single location where the behaviour is configured, and > > the user can either edit /etc/default/ or use debconf. [...] > F

RFS: c3-tool-suite - Cluster Command & Control tool suite

Hi, I've prepared packages for the Cluster Command & Control (C3) tool suite and am know looking for a sponsor. The description reads: The Cluster Command Control (C3) tools are a suite of cluster tools developed at Oak Ridge National Laboratory that are useful for both administration and app

Re: disabling services: update-rc.d vs. /etc/default/

also sprach Tilman Koschnick <[EMAIL PROTECTED]> [2004.12.28.1453 +0100]: > Pro /etc/default/: > - There is one single location where the behaviour is configured, and > the user can either edit /etc/default/ or use debconf. one single location per package. If you want my opinion, then it is time

Re: minimum package name length

Tilman Koschnick <[EMAIL PROTECTED]> wrote: > One question though: Is there any problem if my > c3-tool-suite_4.0.1.orig.tar.gz unpacks into c3-4.0.1/? dpkg-source and > dpkg-buildpackage don't seem to have a problem with it, but are there > any other pitfalls with differing upstream-tarball names

Re: minimum package name length

Am 2004-12-28 15:03:33, schrieb Tilman Koschnick: > One question though: Is there any problem if my > c3-tool-suite_4.0.1.orig.tar.gz unpacks into c3-4.0.1/? dpkg-source and > dpkg-buildpackage don't seem to have a problem with it, but are there > any other pitfalls with differing upstream-tarball

Re: minimum package name length

Am 2004-12-22 00:25:59, schrieb Tilman Koschnick: > Hi, > > I'm intending to package the Cluster Command & Control tool suite [0], > commonly refered to as C3. My package name of choice would be c3, but I > was wondering if such short names are acceptable. Is there any > documentation or general c

Re: minimum package name length

On Thu, 2004-12-23 at 11:16 +0100, Frank Küster wrote: > Tilman Koschnick <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I'm intending to package the Cluster Command & Control tool suite [0], > > commonly refered to as C3. My package name of choice would be c3, but I > > was wondering if such short

disabling services: update-rc.d vs. /etc/default/

Hi, I'm packaging a daemon (gpsd), and I want to give the user the choice if it should be started at boot time or not (it's for GPS receivers, which are most likely not permanently attached to the computer). I have a debconf question to this effect, and currently I am setting a variable in /etc/d