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
based utility (rpm or dpkg, for example). How do I design the consol
On Thu, Feb 13, 2003 at 10:50:04PM +0100, Thomas Viehmann wrote:
> As an additional hinderence, the library has a c++ interface, from
> which the doxygen creates thousands of one-liner .so man-pages. (One
> for each member.) With this strategy, it is painfully clear, that the
> man namespace is utt
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
based utility (rpm or dpkg, for example). How do I design the consol
On Fri, Feb 14, 2003 at 01:43:10AM +0100, Henning Moll wrote:
> Hi!
hello.
> I just build my first binary package. May anybody have a look over it?
> Lintian (woody) reports no errors/warnings, but i think it's still not
> perfect ;-)
could you tell us some more about it first? also, the proper
On Thu, Feb 13, 2003 at 10:50:04PM +0100, Thomas Viehmann wrote:
> As an additional hinderence, the library has a c++ interface, from
> which the doxygen creates thousands of one-liner .so man-pages. (One
> for each member.) With this strategy, it is painfully clear, that the
> man namespace is utt
On Fri, Feb 14, 2003 at 01:43:10AM +0100, Henning Moll wrote:
> Hi!
hello.
> I just build my first binary package. May anybody have a look over it?
> Lintian (woody) reports no errors/warnings, but i think it's still not
> perfect ;-)
could you tell us some more about it first? also, the proper
Hi Jonathan!
You wrote:
> I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
> asked by upstream if I want to maintain the debian/ directory in the
> project's CVS. The RPM .spec file is already done this way. Is there any
> good reason not to do this?
I see very few problems w
Hi Colin.
Colin Watson wrote:
>>Should I have doxygen generate manpages and include them in the -doc
>>package?
[..]
> I think it's a good idea, although I'm biased. :)
That's fair enough. The point that made me think though, is the possibility that
the benefit of man pages declines sharply with
I'm sure I've seen this hashed over in the past, so feel free to point
me at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there
On Thu, Feb 13, 2003 at 08:22:09PM +0100, Thomas Viehmann wrote:
> Should I have doxygen generate manpages and include them in the -doc
> package? Some packages, though not too many, seem to include manpages
> for their library functions and I certainly like them around for libc
> functions and sim
Hi Jonathan!
You wrote:
> I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
> asked by upstream if I want to maintain the debian/ directory in the
> project's CVS. The RPM .spec file is already done this way. Is there any
> good reason not to do this?
I see very few problems w
Hi Colin.
Colin Watson wrote:
>>Should I have doxygen generate manpages and include them in the -doc
>>package?
[..]
> I think it's a good idea, although I'm biased. :)
That's fair enough. The point that made me think though, is the possibility that
the benefit of man pages declines sharply with
I'm sure I've seen this hashed over in the past, so feel free to point
me at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there
Hello.
While working on libchipcard packages, I'm considering to include the api
documentation. Probably this would go in a doc package (html docs alone make
500k package and 4.2M installed).
The documentation is generated by doxygen, which allows many output formats,
amongst others man.
Should I
On Thu, Feb 13, 2003 at 08:22:09PM +0100, Thomas Viehmann wrote:
> Should I have doxygen generate manpages and include them in the -doc
> package? Some packages, though not too many, seem to include manpages
> for their library functions and I certainly like them around for libc
> functions and sim
Hello.
While working on libchipcard packages, I'm considering to include the api
documentation. Probably this would go in a doc package (html docs alone make
500k package and 4.2M installed).
The documentation is generated by doxygen, which allows many output formats,
amongst others man.
Should I
>-Original Message-
>From: Colin Watson [mailto:[EMAIL PROTECTED]
>Sent: Thursday, February 13, 2003 1:20 AM
>To: debian-mentors@lists.debian.org
>Subject: Re: [OT?] Man pages
>
>
>On Wed, Feb 12, 2003 at 06:52:37PM -0800, Barry deFreese wrote:
>> Not sure if this is the proper forum for th
>-Original Message-
>From: Colin Watson [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, February 13, 2003 1:20 AM
>To: [EMAIL PROTECTED]
>Subject: Re: [OT?] Man pages
>
>
>On Wed, Feb 12, 2003 at 06:52:37PM -0800, Barry deFreese wrote:
>> Not sure if this is the proper forum for this question b
Hi,
I just packaged a small game, called GAV (GNU Arcade Volleyball). The
homepage is http://gav.sourceforge.net Here's a screenshot:
http://gav.sourceforge.net/screenshot.php?enlarge=beos_1 It's a remake
of some old DOS game apparently (although I thought I played this on
Atari a long tim
Hi,
I just packaged a small game, called GAV (GNU Arcade Volleyball). The
homepage is http://gav.sourceforge.net Here's a screenshot:
http://gav.sourceforge.net/screenshot.php?enlarge=beos_1 It's a remake
of some old DOS game apparently (although I thought I played this on
Atari a long time
On Wed, Feb 12, 2003 at 06:52:37PM -0800, Barry deFreese wrote:
> Not sure if this is the proper forum for this question but I'll ask
> anywhoo. I am trying to write some man pages and am experiencing some
> wierdness. I pulled down the man mini-HOWTO from LDP and it says to try
> to use the fo
On Thu, Feb 13, 2003 at 12:30:23AM +0100, Michel Dänzer wrote:
> On Mit, 2003-02-12 at 09:44, Sven Luther wrote:
> >
> > I just uploaded a new version of my lablgl package yesterday, and all
> > autobuilder failed with :
> >
> > ocamlmktop -I . -I +labltk -o lablgltop \
> > labltk.cma lablgl.
On Wed, Feb 12, 2003 at 06:52:37PM -0800, Barry deFreese wrote:
> Not sure if this is the proper forum for this question but I'll ask
> anywhoo. I am trying to write some man pages and am experiencing some
> wierdness. I pulled down the man mini-HOWTO from LDP and it says to try
> to use the fo
On Thu, Feb 13, 2003 at 12:30:23AM +0100, Michel Dänzer wrote:
> On Mit, 2003-02-12 at 09:44, Sven Luther wrote:
> >
> > I just uploaded a new version of my lablgl package yesterday, and all
> > autobuilder failed with :
> >
> > ocamlmktop -I . -I +labltk -o lablgltop \
> > labltk.cma lablgl.
> In article <[EMAIL PROTECTED]>, David Grant <[EMAIL PROTECTED]> writes:
> E: gav: changelog-file-not-compressed CHANGELOG
> dpkg-source: cannot represent change to CHANGELOG.gz: binary file
> contents changed
Compress the version you copy into ./debian/tmp/usr/share/doc/,
not
Hi,
David Grant wrote:
> I have a simple package with one binary and a bunch of images should go
> into "/usr/share/games/gav/themes/classic"
>
[...]
>install ./themes/classic/* $(DESTDIR)/usr/share/games/gav/themes/classic
^^^
install installs per default with -rwxr-xr-x
On Wednesday 12 February 2003 21:12, David Grant wrote:
> Hi everyone,
>
> I have a simple package with one binary and a bunch of images should go
> into "/usr/share/games/gav/themes/classic"
>
> I basically modified the upstream Makefile, and changed the install
> target to look as follows:
>
> in
27 matches
Mail list logo
