#66843 closed defect (fixed)
gv @3.7.4_4 does not install (register) its texinfo file in dir file
Reported by: | ballapete (Peter "Pete" Dyballa) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | ||
Port: | gv |
Description
sh-3.2# pushd /opt/local/share/info ; for INFO in *.info ; do INFO="`echo $INFO | awk -F. '{ print $1 }'`"; printf "»» $INFO: "; if [ `grep "\($INFO\)" dir | wc -l` -gt 0 ] ; then echo OK ; else echo "** missing **" ; fi; done
reports
»» gv: ** missing **
All all hints of gv
are missing in dir
file.
install-info gv.info dir
would do the job.
Change History (6)
comment:1 follow-up: 5 Changed 21 months ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… removed |
---|---|
Owner: | set to ryandesign |
Status: | new → assigned |
comment:2 Changed 21 months ago by ryandesign (Ryan Carsten Schmidt)
Apparently there is a gnu_info portgroup that handles the issues related to this.
comment:3 Changed 21 months ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 Changed 21 months ago by ryandesign (Ryan Carsten Schmidt)
comment:5 Changed 21 months ago by ballapete (Peter "Pete" Dyballa)
Replying to ryandesign:
Can you determine why the build system didn't do this?
I was too late on Monterey – after a selfupdate
gv's Portfile
was updated. Here I could see:
DEBUG: activating file: /opt/local/share/man/man1/gv-update-userconfig.1.gz DEBUG: activating file: /opt/local/share/man/man1/gv.1.gz DEBUG: Executing proc-post-org.macports.activate-activate-0 DEBUG: Registering GNU info file /opt/local/share/info/gv.info in /opt/local/share/info/dir using /opt/local/bin/install-info DEBUG: system: /opt/local/bin/install-info /opt/local/share/info/gv.info /opt/local/share/info/dir DEBUG: Executing portactivate::activate_finish DEBUG: Executing org.macports.main (gv)
The INFO file is available.
Note: See
TracTickets for help on using
tickets.
Can you determine why the build system didn't do this? It probably shouldn't be the responsibility of every MacPorts portfile to manually run
install-info
; the build system should do it if it's as necessary as you suggest. If it doesn't do that, you should report that to the authors of the build system so they can fix it.