[bug #62860] [gropdf] trying to access URW fonts from wrong directory

[G. Branden Robinson]

Update of bug #62860 (project groff):

                  Status:               Need Info => Invalid                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #22:


[comment #21 comment #21:]

> As mentioned in [comment #17 comment #17], the
`/usr/local/share/groff/site-font` directory doesn't exist.
> 
> However, I only just noticed that `/usr/local/share/groff` contained other
directories, which are vestiges of the last successful `make && make install`
attempt. I nuked the entire `/usr/local/share/groff` directory, and
reattempted a fresh build of Groff. And—wouldn't you know it—it now builds
fine (tests still fail, though…). Even with the bumped GhostScript version
(10.00.0_1), it built fine.
> 
> I've updated the Gist containing my build run:
>
https://gist.github.com/Alhadis/67fccae66e5e636e71fe68ee6991a2d6/2fd04b1d102abe8de3b61b12f0e2adf864f1ce06
> 
> I feel like shit, because god only knows how much of your time I've wasted
because I never thought to nuke vestiges of a partially overwritten
installation… :(

Don't worry about it.  There are some usability challenges with foundries and
download files and what not, and there will be even if we get our magic font
installer tool written and shipped with the distribution, because simply
accessing and embedding real font files opens a new axis of things that can go
wrong.

I note two things:

1. The "make uninstall" target should help with this sort of issue; it is
touted in the INSTALL.extra file.


Uninstalling
============

If you are dissatisfied with groff, or to prepare for a new installation
from source, you can uninstall it to ensure that no stale files persist
on the system.  Run the command 'make uninstall'.  (If you used 'sudo
make install', run 'sudo make uninstall'.)  At a minimum, some
directories not particular to groff, like 'bin' and (depending on
configuration) an X11 'app-defaults' directory will remain, as will one
plain file called 'dir', created by GNU Texinfo's 'install-info'
command.  (As of this writing, 'install-info' offers no provision for
removing an effectively empty 'dir' file, and groff does not attempt to
parse this file to determine whether it can be safely removed.)  All
other groff artifacts will be deleted from the installation hierarchy.


2.  At the same time, people can create "download" files of their own, and
"make uninstall" won't help to remove things that weren't emplaced by the
"install" target in the first place.

It sounds like this ticket can be resolved since your problem went away, but
bug #62950 remains open.  What you tripped over, others will.  Maybe we can
cushion the fall.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62860>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/