# Breaking the shackles -- A new registry, free of any bounds

**URL:** <https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749>\
**Category:** Community\
**Created:** [November 5, 2019, 2:56pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749 "2019-11-05T14:56:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [November 5, 2019, 2:56pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749/1 "2019-11-05T14:56:17Z")

</div>

For far too long, we have been shackled by the bounds that exist in our daily Julia life. I am, of course, talking about the bounds (upper and lower) that the General registry imposes on us. Instead of the package manager just installing the packages we want, at the versions we want, we get long weird resolver errors preventing us from using the latest and greatest features of our dependencies.

To that, I say: No more!

I would like to announce a new registry called “LivingAtHead” that can be found at [https://github.com/KristofferC/LivingAtHead](https://github.com/KristofferC/LivingAtHead). It is a fork of the General registry, it contains the same packages and the same version of all packages. The only difference is that it contains no upper bounds (and no lower bounds). In other words, it is a liberated version of the General registry.

To start using it, first, get rid of the oppressive General registry:

```julia
(v1.3) pkg> registry rm General
  Removing registry `General` from ~/.julia/registries/General

```

and then, add the new, free and liberal registry, LivingAtHead:

```julia
(v1.3) pkg> registry add https://github.com/KristofferC/LivingAtHead

```

Now just run `Pkg.update()` to get all the new features and start living like a free (wo)man.

Happy Coding,  
Kristoffer “breaker of bounds” Carlsson

PS: This post is not really serious. Don’t report issues to packages using this registry. In fact, don’t report anything to anyone using this registry. Plz. 🙏

---

<div class="post-metadata">

**Author:** ![DIzer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dizer/32/3971_2.png) [@DIzer](https://discourse.julialang.org/u/DIzer)\
**Post date:** [November 9, 2019, 3:22pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749/2 "2019-11-09T15:22:45Z")

</div>

I can not take in. will your registry be synchronizing with the default one over time or not?

---

<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:** [November 9, 2019, 3:33pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749/3 "2019-11-09T15:33:15Z")

</div>

I think this registry is just a tongue-in-cheek demonstration of a point made in this topic:

> [@Please be mindful of version bounds and semantic versioning when tagging your packages](https://discourse.julialang.org/t/please-be-mindful-of-version-bounds-and-semantic-versioning-when-tagging-your-packages/30708/):
>
> In order for packages to be automatically merged into the general registry, it is required that the package’s Project.toml contains a compat section giving upper version bounds on all direct dependencies. I wanted to bring a few concerns to the forefront of the minds of package developers, so that we don’t inadvertently get burned by this practice: Don’t tag your new version as containing breaking changes unless it really does For versions ≥ v"1.0", any time there are version differences of a…

and is not intended to be used for anything serious.

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [November 9, 2019, 3:37pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749/4 "2019-11-09T15:37:23Z")

</div>

> [@Tamas\_Papp](#):
>
> I think this registry is just a tongue-in-cheek demonstration of a point made in this topic:

True (but it does update). I think that it doesn’t put in new packages right now though.

---

<div class="post-metadata">

**Author:** ![anon92994695](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@anon92994695](https://discourse.julialang.org/u/anon92994695)\
**Post date:** [November 9, 2019, 3:39pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749/5 "2019-11-09T15:39:14Z")

</div>

Hahaha - nice experiment. Considering I just had 2 mature dependancies break unexpectedly and break my package this morning I think I’ll be sticking with General :P.
