# Can a Pkg.checkout be REQUIRED?

**URL:** <https://discourse.julialang.org/t/can-a-pkg-checkout-be-required/3165>\
**Category:** General Usage\
**Created:** [April 11, 2017, 10:35am UTC](https://discourse.julialang.org/t/can-a-pkg-checkout-be-required/3165 "2017-04-11T10:35:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JeffreySarnoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeffreysarnoff/32/1980_2.png) [@JeffreySarnoff](https://discourse.julialang.org/u/JeffreySarnoff)\
**Post date:** [April 11, 2017, 10:35am UTC](https://discourse.julialang.org/t/can-a-pkg-checkout-be-required/3165/1 "2017-04-11T10:35:44Z")

</div>

I have a package, ArbFloats, that depends upon the presence of Nemo. The current release version of Nemo does not work with v0.6xx. The current checkout version does. How do I get that built first?

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [April 11, 2017, 11:15am UTC](https://discourse.julialang.org/t/can-a-pkg-checkout-be-required/3165/2 "2017-04-11T11:15:13Z")

</div>

> [@Enforcing latest master in REQUIRE](https://discourse.julialang.org/t/enforcing-latest-master-in-require/2617):
>
> I am wondering if there is a way to request the latest master for a package in REQUIRE. Specifically, I made a PR to a package which has been merged to master, and need it for tests to run, so I put a Pkg.checkout in .travis.yml, but it seems like a hack.

---

<div class="post-metadata">

**Author:** ![JeffreySarnoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeffreysarnoff/32/1980_2.png) [@JeffreySarnoff](https://discourse.julialang.org/u/JeffreySarnoff)\
**Post date:** [April 11, 2017, 2:10pm UTC](https://discourse.julialang.org/t/can-a-pkg-checkout-be-required/3165/3 "2017-04-11T14:10:51Z")

</div>

ok – is there no way to accomplish this without REQUIRE using a build script?

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [April 11, 2017, 2:38pm UTC](https://discourse.julialang.org/t/can-a-pkg-checkout-be-required/3165/4 "2017-04-11T14:38:25Z")

</div>

> [@JeffreySarnoff](#):
>
> ok – is there no way to accomplish this without REQUIRE using a build script?

You can but you shouldn’t. It’s fragile to require a master branch and @tkelman likely won’t accept a release that requires master on another package. Just get them (help them) release the next version instead.

---

<div class="post-metadata">

**Author:** ![fengyang.wang](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fengyang.wang/32/104_2.png) [@fengyang.wang](https://discourse.julialang.org/u/fengyang.wang)\
**Post date:** [April 12, 2017, 9:09am UTC](https://discourse.julialang.org/t/can-a-pkg-checkout-be-required/3165/5 "2017-04-12T09:09:46Z")

</div>

Right; instead of requesting the master branch it’s better to request a specific commit. IIRC that is coming in Pkg3.