Follow-up Comment #7, bug #67268 (group groff):

Quoting http://lists.gnu.org/r/bug-groff/2025-07/msg00018.html :


>> font/devpdf/download: $(devpdffontencdata) $(devpdffontmapdata) \
>> font/devpdf/DESC font/devpdf/Foundry font/devpdf/util/BuildFoundries
>> $(AM_V_GEN)$(MKDIR_P) $(top_builddir)/font/devpdf \
>> && echo "# foundry      ps-font-name    ps-font-file" >$@.tmp \
>> && echo "# A blank foundry is the default." >>$@.tmp \
>> &&


> This is a bit confusing!! Why are you touching download here? We now
> have download.in so why not include your comments in that file - job
> done once.

An oversight.


>> MOSTLYCLEANFILES += font/devpdf/util/BuildFoundries
>> font/devpdf/util/BuildFoundries: \
>> $(devpdf_srcdir)/util/BuildFoundries.pl $(SH_DEPS_SED_SCRIPT) afmtodit
>> $(AM_V_GEN)$(MKDIR_P) $(top_builddir)/font/devpdf/util \
>> # ...snip...
>> && cp -f $(top_srcdir)/font/devpdf/download.in \
>> $(top_builddir)/font/devpdf/download


> This is the important bit and can replace your echo statements above, since
> this is the bit which populates download with Symbol-Slanted.

Yes, except that should happen in the target responsible for creating
the "download" file, not some other file.

>> We shouldn't have two different rules creating "font/devpdf/download".
>> That's just asking for trouble.

> Yes, its the bit I added in the commit before yours. I don't mind if
> it gets run when BuildFoundries is built or when it is run, but we
> don't want the echos.

Agreed.

When replying to Savannah ticket updates by email, the **only** address you
need to reply to is one like this:


To: 108747-bugs-savannah <savannah-track...@gnu.org>


The "fullname" you're given to reply to will be different; it is simply your
numeric Savannah user ID, I think.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to