Oh lord yes...  just call it fgl3  and leave the fgl package alone.
This is a source based community here... so you take a package that
has a dependency on another library and you go out and get that to cover the
dependency and the API is not the same!!!  AND especially if that might be the
only thing you will ever use that lib for ... and you have to stop and rewrite the
original.. and as someone else said with maybe documentation of that API that
is not maybe finished or...  NO ... At that point the person will probably just
DISCARD the compile on the lib or program that had the dependency.. rather
then put the effort in to learn an entire API that doesn't match up.. 
BAD IDEA!!

cheers,
gene