sandbox hashcode in dist directory

2013-11-10 Thread Tim Docker
I'm attempting to use ghc-mod and emacs to get on the fly compiling 
working again. This is always pleasing when it works,
but it seems a never ending challenge to get it to find all my 
dependences :-(


Several of my cabal packages require autogenerated code which used to 
end up in dist/build/autogen. ghc-mod is configured to

search this directory, as per:

https://github.com/kazu-yamamoto/ghc-mod/blob/169069f6232c617f06f24b9caa40f8f967c1cbf5/Language/Haskell/GhcMod/CabalApi.hs#L71

However since starting to use cabal sandboxes, the generated code ends 
up in a directory like this:


dist/dist-sandbox-c4c8b1d4/build/autogen/

What is this hashcode for? Is it always generated when using a sandbox? 
If I have code (like ghc-mod) that needs to access the

build directory, how do I work out the value of the hashcode?

Thanks,

Tim

___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel


Re: sandbox hashcode in dist directory

2013-11-10 Thread Mikhail Glushenkov
Hi,

On Sun, Nov 10, 2013 at 11:26 PM, Tim Docker t...@dockerz.net wrote:

 However since starting to use cabal sandboxes, the generated code ends up in
 a directory like this:

 dist/dist-sandbox-c4c8b1d4/build/autogen/

 What is this hashcode for? Is it always generated when using a sandbox? If I
 have code (like ghc-mod) that needs to access the
 build directory, how do I work out the value of the hashcode?

So that you can use the same add-source dependency with several
different sandboxes and also build it standalone. See discussion in
https://github.com/haskell/cabal/issues/1281

As to how generate the hash code yourself, the relevant part of the
source code is 
https://github.com/haskell/cabal/blob/master/cabal-install/Distribution/Client/Sandbox.hs#L129
That function takes the absolute path to the current sandbox
('/path/to/.cabal-sandbox') as input.


-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel


Re: sandbox hashcode in dist directory

2013-11-10 Thread Tim Docker
Thanks for the quick reply - I'll make an attempt to get ghc-mod to be 
compatible with this.


Tim

On 11/11/13 11:26, Mikhail Glushenkov wrote:

Hi,

On Sun, Nov 10, 2013 at 11:26 PM, Tim Docker t...@dockerz.net wrote:

However since starting to use cabal sandboxes, the generated code ends up in
a directory like this:

 dist/dist-sandbox-c4c8b1d4/build/autogen/

What is this hashcode for? Is it always generated when using a sandbox? If I
have code (like ghc-mod) that needs to access the
build directory, how do I work out the value of the hashcode?

So that you can use the same add-source dependency with several
different sandboxes and also build it standalone. See discussion in
https://github.com/haskell/cabal/issues/1281

As to how generate the hash code yourself, the relevant part of the
source code is 
https://github.com/haskell/cabal/blob/master/cabal-install/Distribution/Client/Sandbox.hs#L129
That function takes the absolute path to the current sandbox
('/path/to/.cabal-sandbox') as input.




___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel


Request to release cabal-install 1.18.0.3 (Was: 2013.4.0.0 proposal

2013-11-10 Thread shelarcy

Hi,

cabal-install 1.18.0.2 has two critical bugs on Windows.


1. cabal sdist command make broken tarball on Windows.

 https://github.com/haskell/cabal/issues/1538


2. cabal update command broke package index sometimes.

  https://twitter.com/xyx_is/status/391944129074044929 (in Japanese)


Both bugs are already fixed in 1.18 branch's cabal-install (with Cabal 
1.18.1.2). But that version isn't released yet. So, please release newer 
version of cabal-install before releasing HP 2013.4.0.0.


Best Regards,


On Mon, 11 Nov 2013 01:46:18 +0900, Johan Tibell johan.tib...@gmail.com wrote:


hashable bump is good. I'm also pro shipping a newer Cabal, if it doesn't
cause any issues with the one that already comes with GHC.


On Sun, Nov 10, 2013 at 5:11 PM, Mark Lentczner mark.lentcz...@gmail.comwrote:


I know it is late, and so I've done some preliminary version sleuthing
Here's my proposal for HP 2013.4.0.0. I know this e-mail's is long - but
hoping to hear from all relevant parties soon.

*GHC 7.6.3* -- this is a compiler bump, but all the included packages
remain at the same version as 2013.2.0.0

*Packages with no changes:*
fgl, haskell-src, html, HTTP, HUnit,
mtl, parsec, QuickCheck, random,
regex-base, regex-compat, regex-posix,
split, stm, text, transformers,
xhtml, zlib

*Packages with minor version bumps:*
*I'll advance these automatically this time - no need for maintainer input*
cgi: 3001.1.7.5 → 3001.1.8.4
network: 2.4.1.2 → 2.4.2.0
parallel: 3.2.0.3 → 3.2.0.4
syb: 0.4.0 → 0.4.1
unordered-containers: 0.2.3.0 → 0.2.3.3
vector: 0.10.0.1 → 0.10.9.1?
primitive: 0.5.0.1 → 0.5.1.0?

*Packages with major version bumps:*
*I'd like to get confirmation from the maintainers of these packages that
this bump is the right thing to do. The bump should ideally only add API,
and not orphan any program that used to compile under the HP - at least not
without a good reason.*
case-insensitive: 1.0.0.1 → 1.1.0.1
hashable: 1.1.2.5 → 1.2.1.0

GLUT: 2.4.0.0 → 2.5.0.1
GLURaw: 1.3.0.0 → 1.4.0.0
OpenGL: 2.8.0.0 → 2.9.1.0
OpenGLRaw: 1.3.0.0 → 1.4.0.0

alex: 3.0.5 → 3.1.0
happy: 1.18.10 → 1.19.0

*New Packages:*
*There was prior discussion on the libraries mailing list, and generally
all around resounding YES! for including aeson.*
*I think we should include it. I'm looking for confirmation from the
maintainer that this is the right version to include.*
aeson: 0.6.2.1

*Cabal:*
*The Cabal 1.18 release was a major new release, including the very very
useful sandbox feature. This would require shipping a different Cabal lib
than the version shipped with the included GHC. I'm not sure of the
implications of doing this - in particular, whether we would have to ship
two Cabal packages or just the later.*
Cabal: 1.16.0 → 1.18.1.2
cabal-install: 1.16.0.2 → 1.18.0.2

What do you all think?

— Mark late, but not forgotten Lentczner

___
Libraries mailing list
librar...@haskell.org
http://www.haskell.org/mailman/listinfo/libraries


--
shelarcy shelarcyhotmail.co.jp
http://page.freett.com/shelarcy/
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel


Re: Request to release cabal-install 1.18.0.3 (Was: 2013.4.0.0 proposal

2013-11-10 Thread Mikhail Glushenkov
Hi,

On Mon, Nov 11, 2013 at 3:50 AM, shelarcy shela...@gmail.com wrote:

 2. cabal update command broke package index sometimes.

   https://twitter.com/xyx_is/status/391944129074044929 (in Japanese)

Do you have a reference to the commit in which that was fixed?



-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel