Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move ARPACK out of Base #27460

Closed
ViralBShah opened this issue Jun 6, 2018 · 8 comments
Closed

Move ARPACK out of Base #27460

ViralBShah opened this issue Jun 6, 2018 · 8 comments
Labels
domain:arrays:sparse Sparse arrays domain:linear algebra Linear algebra kind:excision Removal of code from Base or the repository

Comments

@ViralBShah
Copy link
Member

ViralBShah commented Jun 6, 2018

We now have functioning binary builders in the new JuliaLinearAlgebra org for:

https://github.com/JuliaLinearAlgebra/SuiteSparseBuilder
https://github.com/JuliaLinearAlgebra/ArpackBuilder

We also have

https://github.com/JuliaLinearAlgebra/Arpack.jl

Plan is to move both these libraries out of stdlib into standalone packages.

cc @andreasnoack @staticfloat

@kshyatt kshyatt added domain:linear algebra Linear algebra domain:arrays:sparse Sparse arrays kind:excision Removal of code from Base or the repository labels Jun 6, 2018
@PallHaraldsson
Copy link
Contributor

PallHaraldsson commented Nov 14, 2018

This one is done, right, so issue can be closed?

These where some of the final GPL-licenced, or the last ones, I can't easily locate other ones; except for LGPL-licenced, e.g. GNU MPFR, that's one of the other two issues open with "excision" tag. To me Julia is GPL-free, unless I'm mistaken, as LGPL isn't too much of an issue (or dual-licenced or those with linking-exceptions).

@ViralBShah ViralBShah changed the title Move ARPACK and SuiteSparse out of Base Move ARPACK out of Base Nov 14, 2018
@ViralBShah
Copy link
Member Author

We moved ARPACK out, but there are challenges with SuiteSparse, which we can track separately.

@waldyrious
Copy link
Contributor

We moved ARPACK out

For reference, that was done in #27616

there are challenges with SuiteSparse, which we can track separately.

#27638, I suppose?

@waldyrious
Copy link
Contributor

@ViralBShah since #27638 has been closed, shouldn't the SuiteSparse removal be tracked elsewhere? Either a new issue, or perhaps reopening this one.

@ViralBShah
Copy link
Member Author

At the moment, SuiteSparse and SparseArrays are closely related, and we need to move both together (or else people have to guess what functions are in which package). It is unlikely we will do that as it was quite confusing when we tried it out back then.

@waldyrious
Copy link
Contributor

It is unlikely we will do that

You mean moving both SuiteSparse and SparseArrays out of Base? (Note, I'm just trying to make sure the current thinking and potential next steps are recorded somewhere, since the related issues/PRs seems to be all closed at the moment.)

@ViralBShah
Copy link
Member Author

Yes, it is either move both or no change. At least that is what I concluded.

@ViralBShah
Copy link
Member Author

This discussion is best had in #27638 even though closed (where much of this has happened)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:arrays:sparse Sparse arrays domain:linear algebra Linear algebra kind:excision Removal of code from Base or the repository
Projects
None yet
Development

No branches or pull requests

4 participants