Re: Manpage writing guidelines?
От | Dave Page |
---|---|
Тема | Re: Manpage writing guidelines? |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4850804@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Manpage writing guidelines? (Raphaël Enrici <blacknoz@club-internet.fr>) |
Ответы |
Re: Manpage writing guidelines?
|
Список | pgadmin-hackers |
Hi Raph, There are obviously no guidelines at the moment, so please write whatever seems appropriate for now. I do plan to work on the docs this cycle, so please raise this again then if I forget. Andreas and I were talking about improvingthe doc build just last week (it's perhaps the biggest task for me when packing pgInstaller or pgAdmin at the moment). Regards, Dave. -----Original Message----- From: Raphaël Enrici [mailto:blacknoz@club-internet.fr] Sent: Sun 11/6/2005 12:56 PM To: PgAdmin Hackers; Dave Page; Andreas Pflug Subject: Manpage writing guidelines? To be able to upload to official Debian, I need to have a manpage for each program uploaded in the package. I wrote a long time ago a small manpage for pgadmin3 and I am about to write one for pgagent. Here are some questions: - wouldn't it be a good thing that pgadmin3.1 is pushed out of pkg/debian to a more proper place and included in the make install process? - what tools should we use to write our manpages? Something like xml or whatever? I mean, if we are about to do something to automate html help generation and other thing I'm not aware of, maybe it would be a good thing to unify the way we work. Any ideas? Regards, Raph
В списке pgadmin-hackers по дате отправления: