public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Jay.St.Pierre@Colorado.EDU
To: insight-gnats@sources.redhat.com
Subject: insight/243: broken itcl man pages
Date: Sun, 02 Nov 2003 19:53:00 -0000 [thread overview]
Message-ID: <20031102194320.5177.qmail@sources.redhat.com> (raw)
>Number: 243
>Category: insight
>Synopsis: broken itcl man pages
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Nov 02 19:53:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Jay.St.Pierre@Colorado.EDU
>Release: insight-6.0
>Organization:
>Environment:
Solaris 2.8
>Description:
The itcl/itk man pages are installed with a ".so man.macros" line that cause the man pages to be unparseable. The raw tcl/tk man pages have the same line, but when the get installed this line is replaced with the contents of man.macros. So I just modified the itcl/itk Makefile.in files to include the same installation logic as tcl/tk uses.
The patch I used is attached to this bug report.
>How-To-Repeat:
After you install insight-6.0, attempt to use man or nroff to view an itcl/itk manpage installed in the mann directory. For example, itcl.
>Fix:
diff -ur insight-6.0 insight-6.0.fixed
--- insight-6.0/itcl/itcl/Makefile.in 2003-01-21 13:40:25.000000000 -0700
+++ insight-6.0.fixed/itcl/itcl/Makefile.in 2003-10-31 13:21:56.626003000 -0700
@@ -292,10 +292,12 @@
install-doc: doc
$(mkinstalldirs) $(mandir)/mann
@echo "Installing man pages in $(mandir)"
- @for i in $(srcdir)/doc/*.n; \
+ @cd $(srcdir)/doc; for i in *.n; \
do \
echo "Installing $$i"; \
- $(INSTALL_DATA) $$i $(mandir)/mann ; \
+ sed -e '/man\.macros/r man.macros' -e '/man\.macros/d' \
+ $$i > $(mandir)/mann/$$i; \
+ chmod 444 $(mandir)/mann/$$i; \
done
test: $(TCLSH_PROG)
--- insight-6.0/itcl/itk/Makefile.in 2003-01-21 13:40:29.000000000 -0700
+++ insight-6.0.fixed/itcl/itk/Makefile.in 2003-11-01 14:01:07.273006000 -0700
@@ -287,10 +287,12 @@
install-doc: doc
$(mkinstalldirs) $(mandir)/mann
@echo "Installing man pages in $(mandir)"
- @for i in $(srcdir)/doc/*.n; \
+ @cd $(srcdir)/doc; for i in *.n; \
do \
- echo "Installing $$i info $(mandir)/mann"; \
- $(INSTALL_DATA) $$i $(mandir)/mann ; \
+ echo "Installing $$i in $(mandir)/mann"; \
+ sed -e '/man\.macros/r man.macros' -e '/man\.macros/d' \
+ $$i > $(mandir)/mann/$$i; \
+ chmod 444 $(mandir)/mann/$$i; \
done
test: $(TCLSH_PROG)
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-11-02 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 19:53 Jay.St.Pierre [this message]
2005-09-01 5:32 kseitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031102194320.5177.qmail@sources.redhat.com \
--to=jay.st.pierre@colorado.edu \
--cc=insight-gnats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).