Hi,
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any standard or
recommended way implement this?
--
Manfred Wassmann
PGP and GnuPG public
Hi Manfred!
You wrote:
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any standard or
recommended way implement this?
Well, you could just
On Thu, 10 May 2001, Manfred Wassmann wrote:
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any standard or
recommended way implement this?
Marc Haber [EMAIL PROTECTED] writes:
Do I need to install non-free software if I want to sign packages on
potato?
Neither gpg (with or without RSA) nor the RSA module are non-DFSG,
today, even if one is still sitting in non-free.
Anyway, unless your key is RSA, you don't need the module for
Robert Bihlmeyer [EMAIL PROTECTED] writes:
Since there is no /usr/lib/gnupg/rsa in unstable, would
backporting the unstable gnupg to potato solve this?
Yes, sid's gnupg includes RSA.
Err, huh? potato (2.2r3 at least) has gnupg 1.0.4-1 which includes
RSA.
--
James
--
To
Howdy ya'll ;-)
I've finished packaging my first package for inclusion in Debian now that
I finally got accepted as a maintainer.
It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for
chemistry folks (at least so my girlfriend tells me, and she's a chemistry
major here at
In Warren Anthony Stramiello's email, 10-05-2001:
Howdy ya'll ;-)
I've finished packaging my first package for inclusion in Debian now that
I finally got accepted as a maintainer.
It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for
chemistry folks (at least so my
When you use debmake (the first thing you run on the clean source dir, if
I'm not mistaken), it will create the debian directory. Check in there for
a manpage.1.ex file that serves as a good template for the process.
~Warren
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Eduardo Trapani wrote:
The software I am packaging does not have a man page.
What programs should I use to create one?
I usually just edit one directly (in roff).
I'm pretty sure dh_make installs a sample. If it doesn't, look
at /usr/share/debhelper/dh_make/debian/manpage.1.ex
There's
Eduardo Trapani [EMAIL PROTECTED] writes:
The software I am packaging does not have a man page.
What programs should I use to create one?
Try using help2man to get a good template, and edit it by hand.
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
hi,
On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote:
What programs should I use to create one?
the normal groff and the an macro (on the commandline that's the
-man ;)) ... read the manpage howto as a start and also read man
7 man ...
so long
Othmar
--
To UNSUBSCRIBE,
En réponse à Eduardo Trapani [EMAIL PROTECTED]:
The software I am packaging does not have a man page.
What programs should I use to create one?
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see
hi,
On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote:
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see http://qa.debian.org/man-pages.html for pointers to documentations).
haven't dealt
Y el jueves 10 de mayo, Eduardo Trapani escribió:
The software I am packaging does not have a man page.
What programs should I use to create one?
Thanks, Eduardo.
My suggestion:
Use perldoc, you will write a txt file like this and you will get a
pretty manpage with only one command:
On 10 May 2001 14:58:35 +0200, Robert Bihlmeyer [EMAIL PROTECTED]
wrote:
Maybe removing a stray load-extension rsa is enough?
Yes. Thanks.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber |Questions are the |
Hello, I uploaded a new revision of my packeg hptalx and I'd just received
the following message from [EMAIL PROTECTED] which I don't
understand:
--
There are disparities between your recently installed upload and the
override file for the following file(s):
hptalx_1.1.0-2_i386.deb:
On Wed, May 09, 2001 at 08:43:46AM -0500, Christian T. Steigies wrote:
[...]
It can be debianised, but it can't be included in debian, since it can't
be legally redistributed in binary form.
What do you mean ?? There are lots of packages included in debian in source
form ...
Why
On Thu, 10 May 2001, Ove Kaaven wrote:
On Thu, 10 May 2001, Manfred Wassmann wrote:
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any
After several hours attempting to build debian packages for perl modules
and twenty minutes searching google for helpful documentation, I have
come to the conclusion that I have no frelling idea what I am doing. =)
I read that there is a perl module that would build a package from any
module on
Eric == Eric Van Buggenhaut [EMAIL PROTECTED] writes:
Eric : it can't be included in debian, since it can't be legally
Eric redistributed in binary form.
Eric First part of the sentence might be correct, but not for *that* reason.
Any package that cannot be distributed in the binary
On Thu, May 10, 2001 at 07:27:44PM -0400, Jimmy Kaplowitz wrote:
Hi. I am a novice Debian package maintainer, in the queue for becoming an
official developer. I am maintaining a package called althea, which is an
IMAP email client for GTK+. They have recently added support for SSL through
Hi. I am a novice Debian package maintainer, in the queue for becoming an
official developer. I am maintaining a package called althea, which is an
IMAP email client for GTK+. They have recently added support for SSL through
linking to libssl (from OpenSSL). This is configurable based on the
On Mon, 7 May 2001 21:49:12 +0200, Filip Van Raemdonck
[EMAIL PROTECTED] wrote:
The tools available for automatic changes signing seem to do this for you.
Yes, they do. Judging from the debsign source, this is a gpg issue.
However, debsign fails for me because gpg returns some strange error
Hi,
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any standard or
recommended way implement this?
--
Manfred Wassmann
PGP and GnuPG public
Hi Manfred!
You wrote:
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any standard or
recommended way implement this?
Well, you could just
On Thu, 10 May 2001, Manfred Wassmann wrote:
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any standard or
recommended way implement this?
Marc Haber [EMAIL PROTECTED] writes:
Do I need to install non-free software if I want to sign packages on
potato?
Neither gpg (with or without RSA) nor the RSA module are non-DFSG,
today, even if one is still sitting in non-free.
Anyway, unless your key is RSA, you don't need the module for
Robert Bihlmeyer [EMAIL PROTECTED] writes:
Since there is no /usr/lib/gnupg/rsa in unstable, would
backporting the unstable gnupg to potato solve this?
Yes, sid's gnupg includes RSA.
Err, huh? potato (2.2r3 at least) has gnupg 1.0.4-1 which includes
RSA.
--
James
Howdy ya'll ;-)
I've finished packaging my first package for inclusion in Debian now that
I finally got accepted as a maintainer.
It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for
chemistry folks (at least so my girlfriend tells me, and she's a chemistry
major here at
In Warren Anthony Stramiello's email, 10-05-2001:
Howdy ya'll ;-)
I've finished packaging my first package for inclusion in Debian now that
I finally got accepted as a maintainer.
It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for
chemistry folks (at least so my
* Warren Anthony Stramiello
| a) inclusion in the testing distribution, if still possible
Is handled automagically, if you haven't screwed up anything ;) (that
is, it goes into testing after 10 days of testing in unstable, unless
it has RC bugs, that is). Read more at
The software I am packaging does not have a man page.
What programs should I use to create one?
Thanks, Eduardo.
When you use debmake (the first thing you run on the clean source dir, if
I'm not mistaken), it will create the debian directory. Check in there for
a manpage.1.ex file that serves as a good template for the process.
~Warren
On Thu, May 10, 2001 at 03:52:30PM -0300, Eduardo Trapani wrote:
The software I am packaging does not have a man page.
What programs should I use to create one?
the best, but definitely not the easiest one, is to just get an example page
and edit it by hand. there are programs like manedit
Eduardo Trapani wrote:
The software I am packaging does not have a man page.
What programs should I use to create one?
I usually just edit one directly (in roff).
I'm pretty sure dh_make installs a sample. If it doesn't, look
at /usr/share/debhelper/dh_make/debian/manpage.1.ex
There's
Eduardo Trapani [EMAIL PROTECTED] writes:
The software I am packaging does not have a man page.
What programs should I use to create one?
Try using help2man to get a good template, and edit it by hand.
Falk
En réponse à Eduardo Trapani [EMAIL PROTECTED]:
The software I am packaging does not have a man page.
What programs should I use to create one?
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see
hi,
On Thu, May 10, 2001 at 09:42:51PM +0200, Jérôme Marant wrote:
I would recommend to write them in the POD (Plain Old Documentation)
format which makes it very seasy to write/update a man page.
(see http://qa.debian.org/man-pages.html for pointers to documentations).
haven't dealt
Y el jueves 10 de mayo, Eduardo Trapani escribió:
The software I am packaging does not have a man page.
What programs should I use to create one?
Thanks, Eduardo.
My suggestion:
Use perldoc, you will write a txt file like this and you will get a
pretty manpage with only one command:
Hi. I am a novice Debian package maintainer, in the queue for becoming an
official developer. I am maintaining a package called althea, which is an
IMAP email client for GTK+. They have recently added support for SSL through
linking to libssl (from OpenSSL). This is configurable based on the
On Wed, May 09, 2001 at 08:43:46AM -0500, Christian T. Steigies wrote:
[...]
It can be debianised, but it can't be included in debian, since it can't
be legally redistributed in binary form.
What do you mean ?? There are lots of packages included in debian in source
form ...
Why
Javier Vi uales Guti rrez wrote:
Hello, I uploaded a new revision of my packeg hptalx and I'd just
received
the following message from [EMAIL PROTECTED] which I don't
understand:
I've been getting a rash of them lately. I'm guessing either
packages have moved, or they've recently begun
On Thu, 10 May 2001, Ove Kaaven wrote:
On Thu, 10 May 2001, Manfred Wassmann wrote:
I'm currently writing a manpage which is to be used in a Debian package,
but not exclusively. To be most flexible I want to use variables for path
names that are expanded at build time. Is there any
After several hours attempting to build debian packages for perl modules
and twenty minutes searching google for helpful documentation, I have
come to the conclusion that I have no frelling idea what I am doing. =)
I read that there is a perl module that would build a package from any
module on
44 matches
Mail list logo
