OK, use sandbox and "add-source". But does that address the smart "make" concept? That is, will it automatically rebuild the gloss package if a file in it changed, when I compile the program that imports it? On 4/25/2014 12:39 PM, Brent Yorgey wrote:
On Fri, Apr 25, 2014 at 06:59:04PM +0200, Daniel Trstenjak wrote:
On Fri, Apr 25, 2014 at 11:26:44AM -0500, John M. Dlugosz wrote:
To be specific, in Graphics/Gloss/Internals/Render/Circle.hs
{-# INLINE circleSteps #-} circleSteps :: Float -> Int circleSteps sDiam | sDiam < 8 = 8 | sDiam < 16 = 16 | sDiam < 32 = 32 | otherwise = round sDiam
Ok, I see, if you have to modify such an internal function, then forking the package might really be the only solution.
If you're using a cabal sandbox with 'add-source', then you might not need to rename the gloss package, if cabal first searches for dependencies in the added sources and then on hackage.
Yes, that's what it does. Renaming the package should not be necessary.
-Brent