@Dan, That will support my workflow, thank you, I'll give it a shot
@Bryan, Yes, it is listed. I think the "failed to load interface" error
only happens because of the build/exit failure error. I don't really know
what's going on with the build error. I looked at the log file and it
didn't have any useful information in it.
On Wed, Oct 12, 2016 at 10:44 AM Bryan Richter <b...@chreekat.net> wrote:
> On Wed, Oct 12, 2016 at 09:24:41AM -0700, Sean Hess wrote:
> > Pretty often while developing an application, I realize that some
> > piece of it would be better as an external library published to
> > Hackage. But I don't really know exactly what the interface will look
> > like. I need a way to iterate the package while I'm developing my
> > application, without needing to republish to hackage every time.
> > How do you handle this workflow?
> Stack is designed for this workflow. It looks like you've done
> everything right (but note that including the stack.yaml in the library
> is only strictly necessary for building it independently).
> On SO you list the error as
> Failed to load interface for ‘Network.Worker’
> Does your library list that package under 'exposed-modules' in its Cabal
> You received this message because you are subscribed to a topic in the
> Google Groups "haskell-stack" group.
> To unsubscribe from this topic, visit
> To unsubscribe from this group and all its topics, send an email to
> To post to this group, send email to email@example.com.
> To view this discussion on the web visit
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.