In this case I think you should either make it a separate package, or don't hide it in this module. It looks like an easy way to call Ubigraph from Hhaskell, and there is no apparent alternative (in hackage) so why hide it?
On 13 May 2010 14:52, Gleb Alexeyev <[email protected]> wrote: > Ozgur Akgun wrote: > >> A little bit of topic, but why is the module Graphics.Ubigraph hidden in >> your package? I've been trying to use Ubigraph directly, and your module >> helped me a lot. (I just patched the cabal file to expose >> Graphics.Ubigraph >> as well) >> >> Is there a specific reason for it to be hidden? >> > > There's no reason whatsoever other than vacuum-ubigraph was born rather > hastily and never maintained after that. Its complete history is in the > vacuum-cairo announcement thread: > > http://www.mail-archive.com/[email protected]/msg57214.html > > As you can see, Don Stewart pointed me at Hubigraph, too. If it was on > Hackage, probably the right thing to do would be to drop the hidden module > and use Hubigraph. > > > >> As far as I know, there is another wrapper for Ubigraph in Haskell, >> Hubigraph[1], but it's not on hackage. (licensing issues?) Your module >> contains all the basics, and should be enough in general. >> >> [1] http://ooxo.org/hubigraph/index.html >> >> Best, >> Ozgur >> >> > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe > -- Ozgur Akgun
_______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
