Just to throw another use-case into the pool: I've been looking at how
to create TAGS for downloaded dependencies in my tool
`stack-tag`. Basically, stack-tag creates source tags for the exact
snapshot being used on a project and unifies them in a single TAGS file.

Right now, `stack unpack` fails on GitHub project URLs. I'd like to
understand this problem better but I admit I haven't visited it in a
while.

Regards,

Dan Fithian <daniel.m.fith...@gmail.com> writes:

> Okay, that sounds good. Thanks for the suggestion!
>
> On Sun, Oct 21, 2018 at 1:14 AM Michael Snoyman <mich...@snoyman.com> wrote:
>
>> Given that we're going to be mostly getting rid of that directory, I don't
>> think it makes sense to add it. If the goal is to get access to the source
>> code, using `stack unpack` is the right way to go. We should probably
>> ensure that there's a flag available that will respect any local extra-deps
>> for unpacking.

-- 
Christopher Reichert - https://creichert.io

-- 
You received this message because you are subscribed to the Google Groups 
"haskell-stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to haskell-stack+unsubscr...@googlegroups.com.
To post to this group, send email to haskell-stack@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/haskell-stack/87zhv5sf1n.fsf%40gnus.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: PGP signature

Reply via email to