Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

add-source tarball #48

Open
kowey opened this Issue Feb 6, 2012 · 3 comments

Comments

Projects
None yet
2 participants

kowey commented Feb 6, 2012

If I understand correctly, cabal-dev add-source uses sdist to copy dependencies to a sandbox. For various reasons, however, some packages cannot be effectively packaged using sdist. Perhaps it would make sense if add-source could accept a tarball in addition to the usual directory?

Owner

creswick commented Feb 6, 2012

Oh, this doesn't seem to be documented. add-source does accept a tarball, but it does need to be an sdisted tarball.

However, it sounds like you have tarballs of source dirs that aren't created via sdist -- is there an easy way to tell these apart? We could probably untar to a temp dir and install to the sandbox from that.

kowey commented Feb 8, 2012

Hmm, come to think of it, I don't have any examples that I couldn't address by actually fixing something in the relevant Cabal files. I'll have to dig one up later if I come to that. Sorry! I certainly understand if you feel it's best to close this in the interim

Owner

creswick commented Feb 8, 2012

I've definitely run into this sort of issue before -- packages that won't sdist are more difficult to handle; but I haven't run into a case where a tarball was sitting around (I've only had this happen with bleeding-edge packages from source control).

Let's leave this open a while longer so anyone else can chime in with use cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment