'runghc Setup.lhs sdist' generates tarballs with whacky permissions (Cabal
issue 627 [1]). 'cabal sdist' gets the permissions right but does not allow 
you
to have automatically generated modules (Cabal issue 729 [2]). We have
automatically generated modules so we can't use 'cabal sdist'. So the release
scripts now untars the tarball, adjust permissions, and tars it up again.

[1]: http://hackage.haskell.org/trac/hackage/ticket/627
[2]: http://hackage.haskell.org/trac/hackage/ticket/729

Reinier

Attachments

• resolve-issue1815.dpatch

Hi,

On Sun, Aug 22, 2010 at 07:17:35PM +0000, Reinier Lamers wrote:
> 'runghc Setup.lhs sdist' generates tarballs with whacky permissions (Cabal
> issue 627 [1]). 'cabal sdist' gets the permissions right but does not allow 
> you
> to have automatically generated modules (Cabal issue 729 [2]). We have
> automatically generated modules so we can't use 'cabal sdist'. So the release
> scripts now untars the tarball, adjust permissions, and tars it up again.

> +# fix tarball permissions (Cabal bug 627)
> +# we can't use 'cabal sdist' as a workaround because we have our own sdist hook
> +find $packagename -type f -exec chmod 644 {} +
> +find $packagename -type d -exec chmod 755 {} +
> +
> +tar czf $tarballname $packagename
> +
> +test -f $tarballname
> +cp -f $tarballname $wd/dist/$tarballname
> +
> +# okay, permissions fixed, test if we can build and test from the tarball
Should we rm -rf $packagename here? (out of sheer paranoia)
> +tar xvzf $wd/dist/$tarballname
>  cd $packagename
>  
>  runghc Setup configure --user -ftype-witnesses -ftest

Otherwise, looks OK. Please push at your convenience, I still don't have my
laptop (until Tuesday).

Yours,
   Petr.

This wasn't being tracked by darcswatch