Re: Upstream debian/ dir.

2003-02-17 Thread Jonathan McDowell
On Mon, Feb 17, 2003 at 07:40:56PM +0200, Antti-Juhani Kaijanaho wrote: > On 20030213T213418+, Jonathan McDowell wrote: > > The only drawback I can see is changes in the packaging between > > releases leads to a whole new src tarball to upload to the archive > > rather than just a new diff, but

Re: Upstream debian/ dir.

2003-02-17 Thread Antti-Juhani Kaijanaho
On 20030213T213418+, Jonathan McDowell wrote: > The only drawback I can see is changes in > the packaging between releases leads to a whole new src tarball to > upload to the archive rather than just a new diff, but hopefully this > shouldn't happen too often. I once did this, and usually I le

Re: Upstream debian/ dir.

2003-02-17 Thread Jonathan McDowell
On Mon, Feb 17, 2003 at 07:40:56PM +0200, Antti-Juhani Kaijanaho wrote: > On 20030213T213418+, Jonathan McDowell wrote: > > The only drawback I can see is changes in the packaging between > > releases leads to a whole new src tarball to upload to the archive > > rather than just a new diff, but

Re: Upstream debian/ dir.

2003-02-17 Thread Antti-Juhani Kaijanaho
On 20030213T213418+, Jonathan McDowell wrote: > The only drawback I can see is changes in > the packaging between releases leads to a whole new src tarball to > upload to the archive rather than just a new diff, but hopefully this > shouldn't happen too often. I once did this, and usually I le

New sponsored package submition

2003-02-17 Thread Guilhem BONNEFILLE
Hi, I'm working on a project called Opensched ( http://opensched.sf.net/ ). This project maintain a tool for project scheduling. In order to distribute it, I began a Debian package ( http://nathguil.free.fr/opensched/opensched_0.4.1-1_i386.deb ). I will be really happy if someone can: - che

New sponsored package submition

2003-02-17 Thread Guilhem BONNEFILLE
Hi, I'm working on a project called Opensched ( http://opensched.sf.net/ ). This project maintain a tool for project scheduling. In order to distribute it, I began a Debian package ( http://nathguil.free.fr/opensched/opensched_0.4.1-1_i386.deb ). I will be really happy if someone can: - check

Re: Writing front-ends for programs

2003-02-17 Thread Francesco P. Lovergine
On Thu, Feb 13, 2003 at 09:33:37PM -0800, S Yuval wrote: > Hello, > I'm curius to know how to write user-friendly front ends to programs. > I'm referring to programs like KPakage, GnoRPM, aptitude and dselect and the > various setup utilities for the Apache server that wrap around a console > b

Re: Library documentation

2003-02-17 Thread Francesco P. Lovergine
On Fri, Feb 14, 2003 at 03:48:25AM +, Colin Watson wrote: > > Right, in that case I agree that slews of man pages are probably > inappropriate. If a single man page for the whole library (like > libpng(3)) is possible, then that would be good. > Probably an info tree could be better. Also, G

Re: k3b test package

2003-02-17 Thread Marc Leeman
> Ok, i don't configured http-access very well. So you're not able to browse > there at the moment. But direct access on the *.deb file or using apt-get > should work... > > > Could you provide source packages? See dpkg-source(1) or debuild(1) > > for more info. I seem to have already 2 up-to-d

Re: Writing front-ends for programs

2003-02-17 Thread Francesco P. Lovergine
On Thu, Feb 13, 2003 at 09:33:37PM -0800, S Yuval wrote: > Hello, > I'm curius to know how to write user-friendly front ends to programs. > I'm referring to programs like KPakage, GnoRPM, aptitude and dselect and the > various setup utilities for the Apache server that wrap around a console > b

Re: Library documentation

2003-02-17 Thread Francesco P. Lovergine
On Fri, Feb 14, 2003 at 03:48:25AM +, Colin Watson wrote: > > Right, in that case I agree that slews of man pages are probably > inappropriate. If a single man page for the whole library (like > libpng(3)) is possible, then that would be good. > Probably an info tree could be better. Also, G

Re: k3b test package

2003-02-17 Thread Marc Leeman
> Ok, i don't configured http-access very well. So you're not able to browse > there at the moment. But direct access on the *.deb file or using apt-get > should work... > > > Could you provide source packages? See dpkg-source(1) or debuild(1) > > for more info. I seem to have already 2 up-to-d