Visitar URL original
cabal sdist does not call the sdist build hook in custom Setup.hs · Issue #403 · haskell/cabal · GitHub
Skip to content

cabal sdist does not call the sdist build hook in custom Setup.hs #403

Closed

Description

@bos

(Imported from Trac #410, reported by @dcoutts on 2008-11-20)

The cabal sdist command only runs the default actions, it does not call the sdist hook that gets called if you runghc Setup sdist.

The problem is there is no external method for invoking the sdist hook. Calling ./setup sdist performs the whole action, but we only want to prepare the tree and not tar it up, since cabal sdist uses internal tar code rather than calling an external tar program (which typically does not exist on windows).

Activity

  1. bos commented on May 24, 2012

    @bos
    ContributorAuthor

    (Imported comment by @dcoutts on 2008-11-20)

    See #372.

    What we need is for the command line interface to support generating a tarball image in a given location. That way an external tool like cabal-install can call it and then call tar itself.

  2. jgm commented on Jan 24, 2013

    @jgm

    I just ran into this problem. I was stumped for quite a while wondering why my custom sdist hook wasn't working when I did cabal sdist, then I tried dist/setup/setup sdist and it worked. (Actually I don't need a custom sdist hook, but my Setup.hs uses hookedPreprocessors, adding a custom preprocessor for a new extension, and sdist needs to be aware of this.)

    Any prospect of getting this fixed?

  3. 23Skidoo commented on Apr 28, 2013

    @23Skidoo
    Member

    Calling ./setup sdist performs the whole action, but we only want to prepare the tree and not tar it up

    For sandboxes, we need a way to list all source files of a package. It'd be nice if one could run Setup sdist --list-sources to do that. Right now we do the same thing that cabal sdist does, which results in the same bug.

  4. 23Skidoo commented on Apr 28, 2013

    @23Skidoo
    Member

    I want to fix this for 1.18. Packages with custom preprocessors are really not uncommon.

  5. added 10 commits that reference this issue on May 1, 2013
    30810cb
    256b139
    14ac9f8
    d67edc2
    474c32a
    e68e791
    cebb3e6
    2b68685
    356bae1
    c7aa581
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions