Re: man pages have wrong date
On Sat, Sep 04, 2004 at 09:35:06PM +1000, Scott Smedley wrote: The very last line of all the man pages (with the notable exception of fvwm.1) appears to have an arbitary date (hardcoded from the source man page). I just commited a patch to parse all man pages through config.status. This involved renaming most *.1 files to *.1.in. Several man pages appear to be auto-generated by Perl scripts: ./bin/fvwm-menu-directory.1 ./bin/fvwm-menu-headlines.1 ./bin/fvwm-menu-xlock.1 ./bin/fvwm-perllib.1 ./modules/FvwmDebug/FvwmDebug.1 ./modules/FvwmDebug/FvwmGtkDebug.1 ./modules/FvwmPerl/FvwmPerl.1 ./modules/FvwmWindowMenu/FvwmWindowMenu.1 So I've not changed these. I'm not sure if I need to make any further changes to complete this patch. For example, when making a release, will scripts automatically pickup the new *.1.in files ignore the *.1 files? Yes. Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] pgpm6o0oNVvRr.pgp Description: PGP signature
Re: man pages have wrong date
The very last line of all the man pages (with the notable exception of fvwm.1) appears to have an arbitary date (hardcoded from the source man page). I just commited a patch to parse all man pages through config.status. This involved renaming most *.1 files to *.1.in. Several man pages appear to be auto-generated by Perl scripts: ./bin/fvwm-menu-directory.1 ./bin/fvwm-menu-headlines.1 ./bin/fvwm-menu-xlock.1 ./bin/fvwm-perllib.1 ./modules/FvwmDebug/FvwmDebug.1 ./modules/FvwmDebug/FvwmGtkDebug.1 ./modules/FvwmPerl/FvwmPerl.1 ./modules/FvwmWindowMenu/FvwmWindowMenu.1 So I've not changed these. I'm not sure if I need to make any further changes to complete this patch. For example, when making a release, will scripts automatically pickup the new *.1.in files ignore the *.1 files? SCoTT. :) -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: man pages have wrong date
On Sat, Aug 14, 2004 at 12:53:47PM +1000, Scott Smedley wrote: Create FvwmButtons.1.in, a Makefile entry run it through config.status? (like the fvwm.1 man page) I'm having trouble determining the configuration (in fvwm/Makefile.am?) that creates this target in fvwm/Makefile.in: fvwm.1: $(top_builddir)/config.status fvwm.1.in cd $(top_builddir) $(SHELL) ./config.status $(subdir)/$@ Can anyone offer a clue on how the fvwm.1 target is created? It's the rule man_MANS = fvwm.1 Initially, I created an explicit target: FvwmButtons.1: $(top_builddir)/config.status FvwmButtons.1.in cd $(top_builddir) $(SHELL) ./config.status $(subdir)/$@ in fvwm/modules/FvwmButtons/Makefile.am, but this seems kinda hackish given that the fvwm.1 target is generated automatically. (somehow) Ciao Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] pgp05lcAZ0sr1.pgp Description: PGP signature
Re: man pages have wrong date
On 14 Aug 2004 12:53:47 +1000, Scott Smedley wrote: Create FvwmButtons.1.in, a Makefile entry run it through config.status? (like the fvwm.1 man page) I'm having trouble determining the configuration (in fvwm/Makefile.am?) that creates this target in fvwm/Makefile.in: fvwm.1: $(top_builddir)/config.status fvwm.1.in cd $(top_builddir) $(SHELL) ./config.status $(subdir)/$@ Can anyone offer a clue on how the fvwm.1 target is created? This is done by configure (or more precisely config.status), it converts fvwm.1.in to fvwm.1 and automatically handles Makefile rules. You should just add a name of file to AC_OUTPUT section of configure.in if you want it to be automatically (re)generated. Regards, Mikhael. -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: man pages have wrong date
Create FvwmButtons.1.in, a Makefile entry run it through config.status? (like the fvwm.1 man page) I'm having trouble determining the configuration (in fvwm/Makefile.am?) that creates this target in fvwm/Makefile.in: fvwm.1: $(top_builddir)/config.status fvwm.1.in cd $(top_builddir) $(SHELL) ./config.status $(subdir)/$@ Can anyone offer a clue on how the fvwm.1 target is created? Initially, I created an explicit target: FvwmButtons.1: $(top_builddir)/config.status FvwmButtons.1.in cd $(top_builddir) $(SHELL) ./config.status $(subdir)/$@ in fvwm/modules/FvwmButtons/Makefile.am, but this seems kinda hackish given that the fvwm.1 target is generated automatically. (somehow) SCoTT. :) -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
Re: man pages have wrong date
On Sun, Jul 11, 2004 at 08:01:02PM +1000, Scott Smedley wrote:
I just got confused by the FVWM man pages. The very last line of all the
man pages (with the notable exception of fvwm.1) appears to have an arbitary
date (hardcoded from the source man page).
For example, the FvwmButtons man page from the 2.5.10 release has this line:
3rd Berkeley Distribution 23 September 2002FvwmButtons(1)
You can see all the dates with this command:
find . -name '*.1' -exec /bin/grep ^.TH {} \;
What is the correct solution for this?
Create FvwmButtons.1.in, a Makefile entry run it through config.status?
(like the fvwm.1 man page)
Yes. I've done all this manually in the past, but only when I
remembered.
Additionally, I think it would be nice to specify the version of FVWM
that each man page applies/belongs to in the actual man page. The fvwm.1
man page has this.
Thoughts?
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
pgpW4u4IC5zOU.pgp
Description: PGP signature
