# Distinguishing projects from packages

**URL:** <https://discourse.julialang.org/t/distinguishing-projects-from-packages/153>\
**Category:** Internals & Design\
**Tags:** packages, code-organization, project\
**Created:** [November 7, 2016, 6:37am UTC](https://discourse.julialang.org/t/distinguishing-projects-from-packages/153 "2016-11-07T06:37:58Z")\
**Posts on this page:** 1\
**Showing post:** 35

<div class="post-metadata">

**Author:** ![mauro3](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mauro3/32/292_2.png) [@mauro3](https://discourse.julialang.org/u/mauro3)\
**Post date:** [November 15, 2016, 9:35am UTC](https://discourse.julialang.org/t/distinguishing-projects-from-packages/153/35 "2016-11-15T09:35:01Z")

</div>

Concerning Project vs Packages: why not just standardize where to put runnable scripts into packages as we know them now? Say a folder `run` or `scripts` and the main program would be `run/main.jl`. Pure “Projects” would have an empty `src/` folder and full `run/` folder and vice versa (most would have a bit of both). Similar to `Pkg.test("SomePkg")` we could have a `Pkg.run("SomePkg")` to run `run/main.jl`.

---

_[View the full topic](https://discourse.julialang.org/t/distinguishing-projects-from-packages/153)._