jekor / hesh Goto Github PK

Due to the way that the cabal file is based on the script name, if it shares the name of a package it can create a collision during configuration. A fix would be to give all hesh scripts a fixed/random name and just set the executable name to match the script name.

Not only is the filename not shown when it could be determined (.hs), but the user can't see what their code is being transformed into when it fails to parse.

hesh/Main.hs:30:33: error:
    Module ‘Distribution.Hackage.DB’ does not export ‘readHackage’

hesh/Main.hs:30:46: error:
    Module ‘Distribution.Hackage.DB’ does not export ‘hackagePath’

hesh/Main.hs:33:30: error:
    Module ‘Distribution.Version’ does not export ‘versionBranch’
cabal: Leaving directory '/home/petersen/tmp/cabal-tmp-25299/hesh-1.11.0'

Seems to build okay with haskage-db-1.22 and Data.Version

...otherwise it's confusing (did hesh or my script just hang?).

Example:

/tmp/hesh-a6e68aa65d00a54cfc4c2c09be015560/.cabal-sandbox/x86_64-osx-ghc-7.8.3-packages.conf.d/package.cache: openBinaryFile: does not exist (No such file or directory)

The simple thing is to wipe the directory and try again automatically.

The current method of finding packages is unsophisticated and likely to break in many cases, mainly because it doesn't add constraints to the packages in the cabal file. Additionally, the search for valid versions is not currently 100% correct.

For example, if you use Prelude.read somewhere, it will result in import qualified Prelude.

Multiple packages might share module names. Until there is a more sophisticated way to detect package dependencies, we should provide a method for specifying which package is desired.