# Testing changes to stdlib without remaking the whole of Julia

**URL:** <https://discourse.julialang.org/t/testing-changes-to-stdlib-without-remaking-the-whole-of-julia/11998>\
**Category:** Internals & Design\
**Tags:** question\
**Created:** [June 27, 2018, 3:02pm UTC](https://discourse.julialang.org/t/testing-changes-to-stdlib-without-remaking-the-whole-of-julia/11998 "2018-06-27T15:02:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [February 15, 2019, 2:18pm UTC](https://discourse.julialang.org/t/testing-changes-to-stdlib-without-remaking-the-whole-of-julia/11998/3 "2019-02-15T14:18:31Z")

</div>

Is it also possible to use `Revise.track(Random)` but develop `Random` in a separate folder and not `/path/to/my/julia/share/julia/v1.1/Random/`?

I tried @kristoffer.carlsson’s suggestion in [Editing a package in stdlib - #5 by kristoffer.carlsson](https://discourse.julialang.org/t/editing-a-package-in-stdlib/10199/5) but couldn’t get it to work. The `pushfirst!` doesn’t seem to have any effect.

---

_[View the full topic](https://discourse.julialang.org/t/testing-changes-to-stdlib-without-remaking-the-whole-of-julia/11998)._
