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

Sync with General Registry #155

Open
CarloLucibello opened this issue Oct 8, 2022 · 6 comments
Open

Sync with General Registry #155

CarloLucibello opened this issue Oct 8, 2022 · 6 comments

Comments

@CarloLucibello
Copy link

Why does the general registry point to a very old version of the package? Why the need for a local registry? What makes the packages in this org different from the rest of the ecosystem? I just needed to use ASE.jl in my project and it turned out much harder than expected.

@cortner
Copy link
Member

cortner commented Oct 8, 2022

The MolSim registry allows us to tag versions of packages that are not suitable for general use.

I don't mind tagging ASE, JuLIP and NeighbourLists in the General registry again if there is sufficient interest.

No need to get upset about it. In the meantime using MolSim isn't all that hard - just add the registry and things will work as expected.

@CarloLucibello
Copy link
Author

sorry, that came out a bit harsh due to a few frustrating hours trying to piece together some basic functionalities from the julia ecosystem.

Yes, I would recommend making as many repos as possible available in the General registry, even discovering the local registry takes time and creates friction for casual users, e.g. I landed on this page https://github.com/JuliaMolSim/ASE.jl without having prior knowledge about the org and took me some time to understand what was going on. Also, in my experience local registries are currently quite uncommon for publicly available packages.

Thanks for the quick reply and for the work on those repos!

@cortner
Copy link
Member

cortner commented Oct 10, 2022

@jameskermode - you are using General, can you advise what the best approach is?

@jameskermode
Copy link
Collaborator

I'd also be in favour of including up-to-date versions of ASE.jl and JuLIP.jl in the General registry. My impression is they are no longer changing that rapidly so this should work OK, but if you feel you will need to make further rapid changes within JuliaMolSim then I understand it could be preferable to keep them there exclusively (in which case removing the packages entirely from General might make sense).

Fixing ASE.jl issues #16 and #21 would resolve the biggest problems.

@cortner
Copy link
Member

cortner commented Oct 10, 2022

TBH - I think I'm really the only one using MolSim so I'm tempted to move ASE, JuLIP to General and all the ACE stuff into a new ACE registry, but we'll see...

In fact I think we are close to also moving ACE1.jl and ACE1pack.jl to General. It shouldn't take too much.

@cortner
Copy link
Member

cortner commented Dec 14, 2022

sorry for the delay on this. It took forever to register the neighbourlist (and then I was just too busy and forgot). I'll try to do the same for JuLIP and ASE over christmas and probably ACE1 very soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants