[Slackbuilds-users] fontforge
Dave Woodfall
dave at slackbuilds.org
Wed Oct 21 17:57:45 UTC 2020
On 21/10/20 18:47,
Dave Woodfall <dave at slackbuilds.org> put forth the proposition:
> On 21/10/20 13:33,
> B Watson <yalhcru at gmail.com> put forth the proposition:
> > On 10/21/20, Matteo Bernardini <matteo.bernardini at gmail.com> wrote:
> > >
> > > I was about to test it, but before trying I just want to be sure that
> > > you have noted this bit in fontforge's README
> > >
> > > "NOTE: please remove previous version before building new version."
> > I know from experience that trying to build a new fontforge without
> > following this advice causes a build failure.
> > A question for the maintainer: Why doesn't the SlackBuild check for
> > this and abort or at least warn the user? It could be done with very
> > little code, and would have saved however much time we've collectively
> > spent thinking and writing about it, in this thread.
> I'll add that this week. I do something similar in Qt5 already.
> --
> Dave
> Love is a snowmobile racing across the tundra and then suddenly it flips over,
> pinning you underneath. At night, the ice weasels come.
> --Friedrich Nietzsche
By the way, this usually only happens after a significant update.
Minor changes don't seem to trigger this.
--
Dave
Love is a snowmobile racing across the tundra and then suddenly it flips over,
pinning you underneath. At night, the ice weasels come.
--Friedrich Nietzsche
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20201021/deb07073/attachment.asc>
More information about the SlackBuilds-users
mailing list