What about pointing out to known good version numbers of dependencies in
the ARTIQ documentation?
[:: ] Agreed that that's a better solution. I propose we build into setup.py a
pull of specific version numbers for external dependencies. This makes it
straightforward for end users. And,
I advocate adding options to setup.py to include these dependencies if a user
want's them.
I think it would make sense to fork external dependencies into m-labs/artiq so
that dependencies don't break over time.
I second the motion.
___
ARTIQ
On 01/29/2015 04:25 AM, Slichter, Daniel H. wrote:
I think it would make sense to fork external dependencies into
m-labs/artiq so that dependencies don't break over time.
I second the motion.
What about pointing out to known good version numbers of dependencies in
the ARTIQ documentation?
I advocate adding options to setup.py to include these dependencies if a
user want's them.
I think it would make sense to fork external dependencies into m-labs/artiq
so that dependencies don't break over time.
-Joe
On Wed, Jan 28, 2015 at 8:39 AM, Yann Sionneau y...@m-labs.hk wrote:
Hello,
