Re: [elixir-core:7704] Move Dependency Build files into a seperate location

[Wojtek Mach]

> The _build folder contains all build artifacts for external dependencies 
and internal application code. This means that caching this folder is a 
pain.

Could you elaborate why is this painful? Is it the sheer size of the _build 
directory? Or you don't want to cache app code? Please note that e.g. 
heroku-buildpack-elixir caches the whole _build directory, however uses 
`mix compile --force` to compile the project - this makes sure that your 
app code is always recompiled (works in umbrella too) but the deps are only 
recompiled when they actually change.

W dniu środa, 20 grudnia 2017 08:18:05 UTC+1 użytkownik José Valim napisał:
>
>
> The deps.compile within an umbrella application actually compiles some of 
>> the internal applications. I would actually need to do:
>>
>
> You can still use a Mix task to get the name of the umbrella applications 
> and figure out what you want to cache or not - or even have the mix task 
> doing the caching. It seems clear only relying on the file system is not 
> enough for you but I think you should focus on caching more 
> programmatically rather than expecting Mix to lay out the perfect directory 
> structure for you.
>
> We need a very strong reason to change the _build structure which has been 
> settled from before Elixir v1.0.
> -- 
>
>
> *José Valimwww.plataformatec.com.br 
> Founder and Director of R*
>

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/b10702b2-fd09-4785-ac70-b719925ba90c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elixir-core:7702] Move Dependency Build files into a seperate location

[José Valim]

> The deps.compile within an umbrella application actually compiles some of
> the internal applications. I would actually need to do:
>

You can still use a Mix task to get the name of the umbrella applications
and figure out what you want to cache or not - or even have the mix task
doing the caching. It seems clear only relying on the file system is not
enough for you but I think you should focus on caching more
programmatically rather than expecting Mix to lay out the perfect directory
structure for you.

We need a very strong reason to change the _build structure which has been
settled from before Elixir v1.0.
-- 


*José Valimwww.plataformatec.com.br
Founder and Director of R*

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2B5zmncPwc9V1fsQfSESG%2BZaAAuGsbdPmVQT4KNwb_Yzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elixir-core:7701] Mix should use Checksums for recompilation

[José Valim]

Can you please provide more information on this scenario? When does it
happen? Why does it trigger? How to reproduce it?

Please try to describe the problem as detailed as possible without focusing
on a possible solution.

Using checksums makes the cost of noop much higher, since we need to read
files and compute MD5s, and that would be harmful to development.
-- 


*José Valimwww.plataformatec.com.br
Founder and Director of R*

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2Bs2uzFVxQ4HfyDZWBo-4pJnfGFR7wxfwFQqW9CzqorcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elixir-core:7700] Move Dependency Build files into a seperate location

[Paul Schoenfelder]

That happens because in an umbrella some of your deps are applications in
the umbrella. Separating the build artifacts would still compile the
umbrella applications which are in the dependency tree.

On Wed, Dec 20, 2017 at 12:47 AM  wrote:

> The deps.compile within an umbrella application actually compiles some of
> the internal applications. I would actually need to do:
> mix deps.get
> mix deps.compile
> mix clean
> cache_build_artifacts
> mix compile
> mix test
>
> This is another reason to move the build artifacts to another location for
> deps.
>
>
> On Wednesday, December 20, 2017 at 8:40:28 AM UTC+11, Michał Muskała wrote:
>
>> A solution for this could be to do something like:
>>
>> export MIX_ENV=test
>> mix deps.get
>> mix deps.compile
>> cache_build_artifacts
>> mix compile
>> mix test
>>
>> This should make it possible to cache the dependencies separately from
>> the application.
>>
>> 2017-12-19 22:28 GMT+01:00  :
>> > Ah, so to give some context:
>> > We have a CI pipeline which pulls the deps, builds the umbrella
>> application
>> > and then runs our tests.
>> >
>> > I would like to cache pulling and buildings the deps, and just build
>> the
>> > umbrella application. It would save some time off the CI build. We use
>> mix
>> > to do our compilation, testing and every other command.
>> >
>> > On Tuesday, December 19, 2017 at 4:00:10 PM UTC+11, Paul Schoenfelder
>> wrote:
>> >>
>> >> Could you clarify what the issue is? You haven't specified under what
>> >> circumstances caching is a problem or with what tools.
>> >>
>> >> Paul
>> >>
>> >> On Mon, Dec 18, 2017 at 10:53 PM  wrote:
>> >>>
>> >>> The _build folder contains all build artifacts for external
>> dependencies
>> >>> and internal application code. This means that caching this folder is
>> a
>> >>> pain.
>> >>> If I could simply cache the external dependency build artifacts
>> >>> separately to the internal application artifacts, this would solve my
>> >>> problem. To do this, I think the artifacts should be kept in a
>> seperate
>> >>> location such as _build//deps/...
>> >>>
>> >>>
>> >>>
>> >>> Want to get insights, recommendations and answers from top
>> consultants
>> >>> for free? Head to Discussions to ask questions and find answers.
>> >>>
>> >>> ———
>> >>> This email is intended for the sole use of the intended recipient(s)
>> and
>> >>> may contain information that is confidential and/or privileged.  Any
>> review
>> >>> or distribution by any other person is prohibited.  If you are not an
>> >>> intended recipient, please immediately contact the sender and delete
>> all
>> >>> copies of this email message
>> >>>
>> >>> --
>> >>> You received this message because you are subscribed to the Google
>> Groups
>> >>> "elixir-lang-core" group.
>> >>> To unsubscribe from this group and stop receiving emails from it,
>> send an
>> >>> email to elixir-lang-co...@googlegroups.com.
>> >>> To view this discussion on the web visit
>> >>>
>> https://groups.google.com/d/msgid/elixir-lang-core/ac3428e7-f626-4392-ab3a-9aa32a23face%40googlegroups.com.
>>
>> >>> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>> > Want to get insights, recommendations and answers from top consultants
>> for
>> > free? Head to Discussions to ask questions and find answers.
>> >
>> > ———
>> > This email is intended for the sole use of the intended recipient(s)
>> and may
>> > contain information that is confidential and/or privileged.  Any review
>> or
>> > distribution by any other person is prohibited.  If you are not an
>> intended
>> > recipient, please immediately contact the sender and delete all copies
>> of
>> > this email message
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "elixir-lang-core" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to elixir-lang-co...@googlegroups.com.
>> > To view this discussion on the web visit
>>
> >
>> https://groups.google.com/d/msgid/elixir-lang-core/6d6eabdc-ee00-4a0e-8da3-4762358b8683%40googlegroups.com.
>>
>> >
>> > For more options, visit https://groups.google.com/d/optout.
>>
>
> Want to get insights, recommendations and answers from top consultants for
> free? Head to Discussions  to ask
> questions and find answers.
>
> ———
> This email is intended for the sole use of the intended recipient(s) and
> may contain information that is confidential and/or privileged.  Any review
> or distribution by any other person is prohibited.  If you are not an
> intended recipient, please immediately contact the sender and delete all
> copies of this email message
>
> --
> You received this message because you are subscribed to the Google Groups
> "elixir-lang-core" group.
> To 

[elixir-core:7700] Mix should use Checksums for recompilation

[ls]

The default mix compile to determine if something is stale is to use the 
last-modified time on each file.

https://github.com/elixir-lang/elixir/blob/v1.5.2/lib/mix/lib/mix/utils.ex#L141

A checksum should be used instead to determine if a file has changed rather 
than the last modified time as I have been experiencing issues which cause 
everything to be recompiled when the file hasn't changed.

-- 
Want to get insights, recommendations and answers from top consultants for 
free? Head to Discussions  to ask 
questions and find answers.

———
This email is intended for the sole use of the intended recipient(s) and 
may contain information that is confidential and/or privileged.  Any review 
or distribution by any other person is prohibited.  If you are not an 
intended recipient, please immediately contact the sender and delete all 
copies of this email message

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/98dfa8be-e363-4cc2-8834-b2d76e627394%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elixir-core:7699] Move Dependency Build files into a seperate location

[ls]

The deps.compile within an umbrella application actually compiles some of 
the internal applications. I would actually need to do:
mix deps.get 
mix deps.compile
mix clean
cache_build_artifacts
mix compile
mix test

This is another reason to move the build artifacts to another location for 
deps.

On Wednesday, December 20, 2017 at 8:40:28 AM UTC+11, Michał Muskała wrote:
>
> A solution for this could be to do something like: 
>
> export MIX_ENV=test 
> mix deps.get 
> mix deps.compile 
> cache_build_artifacts 
> mix compile 
> mix test 
>
> This should make it possible to cache the dependencies separately from 
> the application. 
>
> 2017-12-19 22:28 GMT+01:00  : 
> > Ah, so to give some context: 
> > We have a CI pipeline which pulls the deps, builds the umbrella 
> application 
> > and then runs our tests. 
> > 
> > I would like to cache pulling and buildings the deps, and just build the 
> > umbrella application. It would save some time off the CI build. We use 
> mix 
> > to do our compilation, testing and every other command. 
> > 
> > On Tuesday, December 19, 2017 at 4:00:10 PM UTC+11, Paul Schoenfelder 
> wrote: 
> >> 
> >> Could you clarify what the issue is? You haven't specified under what 
> >> circumstances caching is a problem or with what tools. 
> >> 
> >> Paul 
> >> 
> >> On Mon, Dec 18, 2017 at 10:53 PM  wrote: 
> >>> 
> >>> The _build folder contains all build artifacts for external 
> dependencies 
> >>> and internal application code. This means that caching this folder is 
> a 
> >>> pain. 
> >>> If I could simply cache the external dependency build artifacts 
> >>> separately to the internal application artifacts, this would solve my 
> >>> problem. To do this, I think the artifacts should be kept in a 
> seperate 
> >>> location such as _build//deps/... 
> >>> 
> >>> 
> >>> 
> >>> Want to get insights, recommendations and answers from top consultants 
> >>> for free? Head to Discussions to ask questions and find answers. 
> >>> 
> >>> ——— 
> >>> This email is intended for the sole use of the intended recipient(s) 
> and 
> >>> may contain information that is confidential and/or privileged.  Any 
> review 
> >>> or distribution by any other person is prohibited.  If you are not an 
> >>> intended recipient, please immediately contact the sender and delete 
> all 
> >>> copies of this email message 
> >>> 
> >>> -- 
> >>> You received this message because you are subscribed to the Google 
> Groups 
> >>> "elixir-lang-core" group. 
> >>> To unsubscribe from this group and stop receiving emails from it, send 
> an 
> >>> email to elixir-lang-co...@googlegroups.com. 
> >>> To view this discussion on the web visit 
> >>> 
> https://groups.google.com/d/msgid/elixir-lang-core/ac3428e7-f626-4392-ab3a-9aa32a23face%40googlegroups.com.
>  
>
> >>> For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > Want to get insights, recommendations and answers from top consultants 
> for 
> > free? Head to Discussions to ask questions and find answers. 
> > 
> > ——— 
> > This email is intended for the sole use of the intended recipient(s) and 
> may 
> > contain information that is confidential and/or privileged.  Any review 
> or 
> > distribution by any other person is prohibited.  If you are not an 
> intended 
> > recipient, please immediately contact the sender and delete all copies 
> of 
> > this email message 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "elixir-lang-core" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to elixir-lang-co...@googlegroups.com . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/elixir-lang-core/6d6eabdc-ee00-4a0e-8da3-4762358b8683%40googlegroups.com.
>  
>
> > 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
Want to get insights, recommendations and answers from top consultants for 
free? Head to Discussions  to ask 
questions and find answers.

———
This email is intended for the sole use of the intended recipient(s) and 
may contain information that is confidential and/or privileged.  Any review 
or distribution by any other person is prohibited.  If you are not an 
intended recipient, please immediately contact the sender and delete all 
copies of this email message

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/147180e8-d542-4257-b059-90ab3c2f86bd%40googlegroups.com.
For more options, visit 

Re: [elixir-core:7697] Move Dependency Build files into a seperate location

[Paul Schoenfelder]

My approach, at least under Docker, is more or less what Michał showed -
use mix deps.get, deps.compile in one step, cache the results, then do
everything else on top of the cached layer. Your situation should be more
or less identical if I'm understanding you correctly, so I believe that is
all you need here.

Paul

On Tue, Dec 19, 2017 at 3:40 PM, Michał Muskała  wrote:

> A solution for this could be to do something like:
>
> export MIX_ENV=test
> mix deps.get
> mix deps.compile
> cache_build_artifacts
> mix compile
> mix test
>
> This should make it possible to cache the dependencies separately from
> the application.
>
> 2017-12-19 22:28 GMT+01:00  :
> > Ah, so to give some context:
> > We have a CI pipeline which pulls the deps, builds the umbrella
> application
> > and then runs our tests.
> >
> > I would like to cache pulling and buildings the deps, and just build the
> > umbrella application. It would save some time off the CI build. We use
> mix
> > to do our compilation, testing and every other command.
> >
> > On Tuesday, December 19, 2017 at 4:00:10 PM UTC+11, Paul Schoenfelder
> wrote:
> >>
> >> Could you clarify what the issue is? You haven't specified under what
> >> circumstances caching is a problem or with what tools.
> >>
> >> Paul
> >>
> >> On Mon, Dec 18, 2017 at 10:53 PM  wrote:
> >>>
> >>> The _build folder contains all build artifacts for external
> dependencies
> >>> and internal application code. This means that caching this folder is a
> >>> pain.
> >>> If I could simply cache the external dependency build artifacts
> >>> separately to the internal application artifacts, this would solve my
> >>> problem. To do this, I think the artifacts should be kept in a seperate
> >>> location such as _build//deps/...
> >>>
> >>>
> >>>
> >>> Want to get insights, recommendations and answers from top consultants
> >>> for free? Head to Discussions to ask questions and find answers.
> >>>
> >>> ———
> >>> This email is intended for the sole use of the intended recipient(s)
> and
> >>> may contain information that is confidential and/or privileged.  Any
> review
> >>> or distribution by any other person is prohibited.  If you are not an
> >>> intended recipient, please immediately contact the sender and delete
> all
> >>> copies of this email message
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "elixir-lang-core" group.
> >>> To unsubscribe from this group and stop receiving emails from it, send
> an
> >>> email to elixir-lang-co...@googlegroups.com.
> >>> To view this discussion on the web visit
> >>> https://groups.google.com/d/msgid/elixir-lang-core/
> ac3428e7-f626-4392-ab3a-9aa32a23face%40googlegroups.com.
> >>> For more options, visit https://groups.google.com/d/optout.
> >
> >
> > Want to get insights, recommendations and answers from top consultants
> for
> > free? Head to Discussions to ask questions and find answers.
> >
> > ———
> > This email is intended for the sole use of the intended recipient(s) and
> may
> > contain information that is confidential and/or privileged.  Any review
> or
> > distribution by any other person is prohibited.  If you are not an
> intended
> > recipient, please immediately contact the sender and delete all copies of
> > this email message
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "elixir-lang-core" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to elixir-lang-core+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/elixir-lang-core/
> 6d6eabdc-ee00-4a0e-8da3-4762358b8683%40googlegroups.com.
> >
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "elixir-lang-core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elixir-lang-core+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/elixir-lang-core/CAGAFNpkAbD3cGZNnnkERPeBY8%3DXg6FsuLAny%3D8nxbA%
> 2BiM1ktRQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/CAK%3D%2B-Ttra8Fpvc11-9Rzm2wO05Dc_u4-F%2B-oWqZc5XRorMEk1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elixir-core:7696] Move Dependency Build files into a seperate location

[Michał Muskała]

A solution for this could be to do something like:

export MIX_ENV=test
mix deps.get
mix deps.compile
cache_build_artifacts
mix compile
mix test

This should make it possible to cache the dependencies separately from
the application.

2017-12-19 22:28 GMT+01:00  :
> Ah, so to give some context:
> We have a CI pipeline which pulls the deps, builds the umbrella application
> and then runs our tests.
>
> I would like to cache pulling and buildings the deps, and just build the
> umbrella application. It would save some time off the CI build. We use mix
> to do our compilation, testing and every other command.
>
> On Tuesday, December 19, 2017 at 4:00:10 PM UTC+11, Paul Schoenfelder wrote:
>>
>> Could you clarify what the issue is? You haven't specified under what
>> circumstances caching is a problem or with what tools.
>>
>> Paul
>>
>> On Mon, Dec 18, 2017 at 10:53 PM  wrote:
>>>
>>> The _build folder contains all build artifacts for external dependencies
>>> and internal application code. This means that caching this folder is a
>>> pain.
>>> If I could simply cache the external dependency build artifacts
>>> separately to the internal application artifacts, this would solve my
>>> problem. To do this, I think the artifacts should be kept in a seperate
>>> location such as _build//deps/...
>>>
>>>
>>>
>>> Want to get insights, recommendations and answers from top consultants
>>> for free? Head to Discussions to ask questions and find answers.
>>>
>>> ———
>>> This email is intended for the sole use of the intended recipient(s) and
>>> may contain information that is confidential and/or privileged.  Any review
>>> or distribution by any other person is prohibited.  If you are not an
>>> intended recipient, please immediately contact the sender and delete all
>>> copies of this email message
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "elixir-lang-core" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to elixir-lang-co...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/elixir-lang-core/ac3428e7-f626-4392-ab3a-9aa32a23face%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>
>
> Want to get insights, recommendations and answers from top consultants for
> free? Head to Discussions to ask questions and find answers.
>
> ———
> This email is intended for the sole use of the intended recipient(s) and may
> contain information that is confidential and/or privileged.  Any review or
> distribution by any other person is prohibited.  If you are not an intended
> recipient, please immediately contact the sender and delete all copies of
> this email message
>
> --
> You received this message because you are subscribed to the Google Groups
> "elixir-lang-core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elixir-lang-core+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elixir-lang-core/6d6eabdc-ee00-4a0e-8da3-4762358b8683%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/CAGAFNpkAbD3cGZNnnkERPeBY8%3DXg6FsuLAny%3D8nxbA%2BiM1ktRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elixir-core:7696] Move Dependency Build files into a seperate location

[ls]

Ah, so to give some context:
We have a CI pipeline which pulls the deps, builds the umbrella application 
and then runs our tests.

I would like to cache pulling and buildings the deps, and just build the 
umbrella application. It would save some time off the CI build. We use mix 
to do our compilation, testing and every other command.

On Tuesday, December 19, 2017 at 4:00:10 PM UTC+11, Paul Schoenfelder wrote:
>
> Could you clarify what the issue is? You haven't specified under what 
> circumstances caching is a problem or with what tools.
>
> Paul 
>
> On Mon, Dec 18, 2017 at 10:53 PM  wrote:
>
>> The _build folder contains all build artifacts for external dependencies 
>> and internal application code. This means that caching this folder is a 
>> pain.
>> If I could simply cache the external dependency build artifacts 
>> separately to the internal application artifacts, this would solve my 
>> problem. To do this, I think the artifacts should be kept in a seperate 
>> location such as _build//deps/...
>>
>>
>>
>> Want to get insights, recommendations and answers from top consultants 
>> for free? Head to Discussions  to ask 
>> questions and find answers.
>>
>> ———
>> This email is intended for the sole use of the intended recipient(s) and 
>> may contain information that is confidential and/or privileged.  Any review 
>> or distribution by any other person is prohibited.  If you are not an 
>> intended recipient, please immediately contact the sender and delete all 
>> copies of this email message
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elixir-lang-core" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elixir-lang-co...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elixir-lang-core/ac3428e7-f626-4392-ab3a-9aa32a23face%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
-- 
Want to get insights, recommendations and answers from top consultants for 
free? Head to Discussions  to ask 
questions and find answers.

———
This email is intended for the sole use of the intended recipient(s) and 
may contain information that is confidential and/or privileged.  Any review 
or distribution by any other person is prohibited.  If you are not an 
intended recipient, please immediately contact the sender and delete all 
copies of this email message

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/6d6eabdc-ee00-4a0e-8da3-4762358b8683%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[elixir-core:7694] Elixir v1.5.3 released

[José Valim]

It is a maintenance release, so nothing out of the ordinary.

Please see the release notes for more information:
https://github.com/elixir-lang/elixir/releases/tag/v1.5.3


*José Valimwww.plataformatec.com.br
Founder and Director of R*

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4KuWz4y79k_w0hwhBtFmLKuXLDBXQhZG9FzBbL40sfHhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [elixir-core:7693] Move Dependency Build files into a seperate location

[Louis Pilfold]

Hi gang

There's a mix task that will remove compiled application code (clean, I
think). Run this before caching the build directory :)

Cheers,
Louis

On Tue, 19 Dec 2017, 04:59 Paul Schoenfelder, 
wrote:

> Could you clarify what the issue is? You haven't specified under what
> circumstances caching is a problem or with what tools.
>
> Paul
>
> On Mon, Dec 18, 2017 at 10:53 PM  wrote:
>
>> The _build folder contains all build artifacts for external dependencies
>> and internal application code. This means that caching this folder is a
>> pain.
>> If I could simply cache the external dependency build artifacts
>> separately to the internal application artifacts, this would solve my
>> problem. To do this, I think the artifacts should be kept in a seperate
>> location such as _build//deps/...
>>
>>
>>
>> Want to get insights, recommendations and answers from top consultants
>> for free? Head to Discussions  to ask
>> questions and find answers.
>>
>> ———
>> This email is intended for the sole use of the intended recipient(s) and
>> may contain information that is confidential and/or privileged.  Any review
>> or distribution by any other person is prohibited.  If you are not an
>> intended recipient, please immediately contact the sender and delete all
>> copies of this email message
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "elixir-lang-core" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to elixir-lang-core+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elixir-lang-core/ac3428e7-f626-4392-ab3a-9aa32a23face%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "elixir-lang-core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elixir-lang-core+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elixir-lang-core/CAK%3D%2B-Tsp3Q6HbzrE1kJ0Th1GUAxreZyVckU7d4kFY_8JfmAoCg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elixir-lang-core+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elixir-lang-core/CABu8xFBpCQ9M6c%2B5%3D1vdqqkyaf0kKxfw6Z0xekyxfj7Sdq6S9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.