# List of working packages on v. 1.0

**URL:** <https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779>\
**Category:** New to Julia\
**Created:** [August 20, 2018, 6:30pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779 "2018-08-20T18:30:12Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![LeoK987](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/leok987/32/4880_2.png) [@LeoK987](https://discourse.julialang.org/u/LeoK987)\
**Post date:** [August 21, 2018, 12:41am UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/21 "2018-08-21T00:41:05Z")

</div>

Why don’t we do it in the open-source way? Allow anyone who has tested/used any packages that work for him post their names into an open list.

---

<div class="post-metadata">

**Author:** ![Neonlights](https://avatars.discourse-cdn.com/v4/letter/n/a698b9/32.png) [@Neonlights](https://discourse.julialang.org/u/Neonlights)\
**Post date:** [August 24, 2018, 1:51pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/22 "2018-08-24T13:51:32Z")

</div>

As somebody who just decided to start using Julia, I have to say that it is incredibly frustrating to hit ] add SomePackage, then find out it can’t be installed.  
This is exactly how to stop people taking up the language.

---

<div class="post-metadata">

**Author:** ![St0n](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/st0n/32/4126_2.png) [@St0n](https://discourse.julialang.org/u/St0n)\
**Post date:** [August 24, 2018, 5:30pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/23 "2018-08-24T17:30:49Z")

</div>

Unfortunately Neonlights tells true fakts. Actually im trying to run Seismic.jl and GMT.jl and both dont work. I would really like to know, if its just anythink that i’m missing or if voth packages dont work in version 1.0.  
Lukyly i have worked with Julia for a while, so i wont give up on the language… For new users, this could be the other way round

---

<div class="post-metadata">

**Author:** ![rdeits](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rdeits/32/286_2.png) [@rdeits](https://discourse.julialang.org/u/rdeits)\
**Post date:** [August 24, 2018, 5:33pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/24 "2018-08-24T17:33:33Z")

</div>

Please realize that you are complaining about the work of volunteers who are doing this largely for free and largely for the benefit of others.

If you want the situation to improve, join us in the `#upgradathon` channel on Slack and help us make a difference. Otherwise please be patient.

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [August 24, 2018, 5:36pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/25 "2018-08-24T17:36:42Z")

</div>

Providing feedback is part of contributing. And is not like they are not willing to do work and are just complaining. They are assessing the current status and asking about an alternative which is to provide a platform to contribute. @Keno already have the results from previous runs, so even if it is a Google spreadsheet with OK and not OK that would work and people can test the latest release locally and crowdsource that information.

Many developers have partial knowledge of the ecosystem since we already had to verify the status of the dependencies for our projects, but new users might lack even such.

---

<div class="post-metadata">

**Author:** ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)\
**Post date:** [August 24, 2018, 5:38pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/26 "2018-08-24T17:38:56Z")

</div>

@quinnj put together a spreadsheet from the PkgEval run earlier this week: I don’t think it makes too much sense to try to hand-curate it, but hopefully that gives some idea at least: [PkgEvalResults - Google Sheets](https://docs.google.com/spreadsheets/d/1Q_FKJuYYiro1UjHjm1gHdGh47Vo1VMVm9LwjdGR9UBM/edit#gid=40571623)

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [August 24, 2018, 5:41pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/27 "2018-08-24T17:41:41Z")

</div>

Thanks! Would be nice to have the release tested to know if one should expect a change in the status.  
@quinnj Thanks.

---

<div class="post-metadata">

**Author:** ![rdeits](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/rdeits/32/286_2.png) [@rdeits](https://discourse.julialang.org/u/rdeits)\
**Post date:** [August 24, 2018, 5:42pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/28 "2018-08-24T17:42:04Z")

</div>

Cool! I’m excited to see how this changes with the next update now that the Images.jl and WebIO.jl stacks are working on 1.0.

---

<div class="post-metadata">

**Author:** ![quinnj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/quinnj/32/11_2.png) [@quinnj](https://discourse.julialang.org/u/quinnj)\
**Post date:** [August 24, 2018, 5:56pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/29 "2018-08-24T17:56:04Z")

</div>

Happy to keep updating it as @keno shares new PkgEval results; it’s pretty easy to update.

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [August 24, 2018, 6:41pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/30 "2018-08-24T18:41:03Z")

</div>

> [@St0n](#):
>
> Actually im trying to run Seismic.jl and GMT.jl and both dont work.

Why do you say that GMT.jl doesn’t work? Tests clearly show that it does (despite what’s in Keno’s [link](https://docs.google.com/spreadsheets/d/1Q_FKJuYYiro1UjHjm1gHdGh47Vo1VMVm9LwjdGR9UBM/edit#gid=40571623)) and I’m currently working on it right now adding more modules, so good time to submit issues.

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [August 24, 2018, 6:43pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/31 "2018-08-24T18:43:54Z")

</div>

> [@quinnj](#):
>
> Happy to keep updating it as @keno shares new PkgEval results; it’s pretty easy to update

How is that information generated? I see that it says that GMT fails but it [doesn’t](https://travis-ci.org/GenericMappingTools/GMT.jl)

---

<div class="post-metadata">

**Author:** ![Tero\_Frondelius](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tero_frondelius/32/7629_2.png) [@Tero\_Frondelius](https://discourse.julialang.org/u/Tero_Frondelius)\
**Post date:** [August 24, 2018, 7:12pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/32 "2018-08-24T19:12:54Z")

</div>

Master passes but probably new version is not yet tagged. Keno is testing released packages.

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [August 24, 2018, 7:25pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/33 "2018-08-24T19:25:42Z")

</div>

Tagged version passed as well.

---

<div class="post-metadata">

**Author:** ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)\
**Post date:** [August 24, 2018, 7:34pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/34 "2018-08-24T19:34:29Z")

</div>

You’re asking your users to manually install a binary dependency. PkgEval doesn’t read READMEs 😉 . It runs Pkg.add in a fairly minimal Linux environment (very few things work, no compiler, only basic utils installed) and then tries to run the tests.

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [August 24, 2018, 7:54pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/35 "2018-08-24T19:54:18Z")

</div>

Right, but couldn’ it use the info of Travis-CI instead?

---

<div class="post-metadata">

**Author:** ![Nosferican](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nosferican/32/9275_2.png) [@Nosferican](https://discourse.julialang.org/u/Nosferican)\
**Post date:** [August 24, 2018, 8:00pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/36 "2018-08-24T20:00:49Z")

</div>

I can make a script that just takes the status from the Travis CI API… I ran it a couple weeks back for a paper on various languages using R, but can make the script in Julia available.

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [August 24, 2018, 8:12pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/37 "2018-08-24T20:12:07Z")

</div>

The ideal solution would be to try using BinaryBuilder and BinaryProvider to install this dependency for your users when they do a `Pkg.add`. I know it’s a major pain, but those new tools aim to make it easier. I highly recommend Elliot’s talk from this year’s JuliaCon as an introduction.

It seems fair to evaluate based upon what a user would experience with a `Pkg.add` alone.

---

<div class="post-metadata">

**Author:** ![Keno](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/keno/32/285_2.png) [@Keno](https://discourse.julialang.org/u/Keno)\
**Post date:** [August 24, 2018, 8:12pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/38 "2018-08-24T20:12:07Z")

</div>

> [@joa-quim](#):
>
> Right, but couldn’ it use the info of Travis-CI instead?

No, the point of PkgEval is to evaluate the experience of a user who just does Pkg.add.

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [August 24, 2018, 8:24pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/39 "2018-08-24T20:24:47Z")

</div>

I haven’t looked at it carefully yet but from a quick look I got the impression that windows binaries are built with gcc, right? That’s a hard pill for me to swallow as I’m the guy who builds gmt (not the wrapper) for windows an I’m quite keen to keep doing it with VS.

---

<div class="post-metadata">

**Author:** ![St0n](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/st0n/32/4126_2.png) [@St0n](https://discourse.julialang.org/u/St0n)\
**Post date:** [August 24, 2018, 8:37pm UTC](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/40 "2018-08-24T20:37:28Z")

</div>

Hey joa-quim,  
youre right: i managed to run GMT now. In fact it was because i tryed to use a 4.xx version istead the 5.xx version of GMT, so it was my failure. But to answer your Question: I did say GMT didn’t work because it didn’t worked for me at that time and i was not able to find out if that was because of Julia Version problems or because i am doing something wrong (wich was so). And as you pointed out… theres no List to trust right now.  
My Seismic.jl problem still exists.  
What i was NOT willing to say was any proven fact about a package running or not. Sorry if my post was creating that apperance

[Previous page](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779.md?page=1)

[Next page](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779.md?page=3)