Proper and eunit for sinan escript

[Tristan Sloughter]

So after giving my lightning talk on sinan with my thinkpad I gave it again via Ram's macbook and 'sinan dist' failed. Another guy was following along and got the same error which he added on github issues: https://github.com/erlware/sinan/issues/79

I see Eric provided a solution and is working on making it easier, but why does it even need proper and eunit to build a project? Unless I want to run tests it shouldn't matter, right?

Tristan

[Eric Merritt]

The problem is that sinan currently inserts them as compile time
dependencies in every project regardless of whether or not they are
actual compile time dependencies. It would probably be best to do a
check and actually see if there are eunit or proper dependencies
before inserting either as dependencies. That would probably solve a
lot of problems actually. I didnt think of it until just now though.

Eric

> --
> You received this message because you are subscribed to the Google Groups
> "erlware-questions" group.
> To post to this group, send email to erlware-...@googlegroups.com.
> To unsubscribe from this group, send email to
> erlware-questi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/erlware-questions?hl=en.

[Tristan Sloughter]

Any movement on a solution to this?

If it is made to work without needed those deps I'll make an announcement, a number of people will try it when that happens I think.

Tristan

[Eric Merritt]

It has not been high on my list. However, its a pretty easy change
even if it is *not* backwards compatible. Well there are probably not
a lot of folks using proper/cucumberl so those going away wont hurt
anything. Eunit becoming something you have to stick in the
compile-time dependencies will.

That's the only thing I am worried about in this case.

[eigenfunction]

Well, i use cucumberl, but i can do without it if that is a show
stopper.
Cheers.

On 18 Apr., 18:42, Eric Merritt <ericbmerr...@gmail.com> wrote:
> It has not been high on my list. However, its a pretty easy change
> even if it is *not* backwards compatible. Well there are probably not
> a lot of folks using proper/cucumberl so those going away wont hurt
> anything. Eunit becoming something you have to stick in the
> compile-time dependencies will.
>
> That's the only thing I am worried about in this case.
>
> On Wed, Apr 18, 2012 at 11:34 AM, Tristan Sloughter
>
>
>
>
>
>
>
> <tristan.slough...@gmail.com> wrote:
> > Any movement on a solution to this?
>
> > If it is made to work without needed those deps I'll make an announcement, a
> > number of people will try it when that happens I think.
>
> > Tristan
>

> > On Sat, Mar 31, 2012 at 6:05 PM, Eric Merritt <ericbmerr...@gmail.com>

[Eric Merritt]

On no you can still use it. You will just have to add an explicit
compile time dependency to your sinan.config. Don't worry I use it a
ton too it wont go away.

That constraint is currently implicit in all projects and it really
shouldn't be. So it will just become explicit.