On Mon, 2020-05-11 at 02:03 +0100, Ken Moffat via blfs-dev wrote: > Usually, I can work out whether dependencies don't apply (e.g. > packages only relevant to OSX), but for the current version of > fontforge I'm having difficulty about how to treat 'git'. > > On my normal build git is of course installed, and cmake reports > the version it found. Looking at the cmake files it seems as if > this is needed so that it can report the git version which was used > for a build from git (i.e. not a release), and it certainly builds > ok if I hide git. > > So, my question is: should I not mention git in the dependencies > (and wait for some smart alec to complain that it tests for git), or > do something else ?
I think more and more build systems test for git (meson almost systematically does, but even some configure scripts). Up to now, I've always seen a fallback, so git is optional. I think git should be added to optional deps in this case. Since you have spent some time on it, it will show ;) Also, knowing that it depends optionally on git may help investigating bugs resulting of git usage, if any. But I agree that having git in the opt deps is not very useful... > > More generally with cmake, I get the distinct impression that > finding out *how* cmake determines if a program/library is present > was specified by a devotee of Anoia (the goddess of things stuck in > drawers) - So do I > > [...] > Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
