-
Notifications
You must be signed in to change notification settings - Fork 481
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
New package: SAMtools v0.0.1 #16341
New package: SAMtools v0.0.1 #16341
Conversation
JuliaRegistrator
commented
Jun 14, 2020
•
edited
Loading
edited
- Registering package: SAMtools
- Repository: https://github.com/aramirezreyes/SAMtools.jl
- Created by: @aramirezreyes
- Version: v0.0.1
- Commit: 1ab4a07bbe9127356d6b9410ca0a6f316f459f2b
- Reviewed by: @aramirezreyes
- Reference: aramirezreyes/AvailablePotentialEnergyFramework.jl@1ab4a07#commitcomment-39887966
Your Since you are registering a new package, please make sure that you have read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1 If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text |
a06d2a8
to
92a223e
Compare
UUID: ce1b76f3-601c-5192-adf8-a07e935792b9 Repo: https://github.com/aramirezreyes/SAMtools.jl.git Tree: d93699a0e0152f698c8d98267027f9fbbab6b47c Registrator tree SHA: 58e84c9733c0606ca53349dbce519209d8a8402b
92a223e
to
8bbb80c
Compare
Why did you rename this? I will revert this merge because we can't have two folders called |
This reverts commit 1f7ade1.
This should probably also have failed CI IMO? cc @DilumAluthge We don't really have any written out guidelines about multiple packages with the same name, or packages with cases shifted like this. Would be good to spell out that. |
There are really two packages I think: |
Ah, thought it was by the same author. |
Isn't that even worse? It is not a rename but a package got overwritten. Checking the |
It didn't get overwritten, it was fully functional on file systems that can differentiate by letter cases. |
These are two different packages, both in early stage.
I never thought it could be a problem for some systems that cannot
differentiate letter cases. If that is the case, please feel free to
revert.
I looked for the guidelines and didn't see something related to whether
those names are different or equal. Although I agree they can cause
confusion.
El mié., 17 jun 2020 2:00 a. m., Fredrik Ekre <[email protected]>
escribió:
… It didn't get overwritten, it was fully functional on file systems that
can differentiate by letter cases.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16341 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVLG6JMLXMEM5VR2EPKZ5LRXCAZZANCNFSM4N5HUKGQ>
.
|
Yea it's not your fault. Hopefully the packages do similar things so maybe it makes sense to join efforts. |
I renamed my package, should I create a new UUID before trying to register with the new name? |