Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ciarán O'Mara
    @CiaranOMara
    @BenJWard the new GFF3.jl will need to require Indexes.jl, which is yet to be registered. I haven’t access to setup attobot or the Documenter.jl keys in Travis to finish up and register Indexes.jl.
    Ben J. Ward
    @BenJWard
    Hey @CiaranOMara Ok I'll alter the permissions.
    I'm considering putting any new repos that are not released yet, into a BioJulia based registry rather than through attobot and METADATA. Pkg 3 now allows us to create such custom registries.
    Ciarán O'Mara
    @CiaranOMara
    I’ll have to watch and admire the development of a BioJulia based registry. That’s not an aspect of Julia I’m familiar with.
    Do you know if a BioJulia based registry will allow users to continue to do ]add package_x from the REPL?
    Ben J. Ward
    @BenJWard
    Yes it would
    The user can add custom registries using ]registries add URL or something similar, after which the usualy package adding and update should work as usual
    Ciarán O'Mara
    @CiaranOMara
    That was my next question - would a user need to additionally add the BioJulia registery?
    Ben J. Ward
    @BenJWard
    (v1.1) pkg> registry add git@github.com:HolyLab/HolyLabRegistry.git
       Cloning registry from "git@github.com:HolyLab/HolyLabRegistry.git"
         Added registry `HolyLabRegistry` to `~/.julia/registries/HolyLabRegistry`
    This is how it goes when I add Tim Holy's Lab Registry
    So it's straightforward enough
    I added you as an admin collaborator of GFF3, IIRC that should let you set up documenter
    Ben J. Ward
    @BenJWard
    I've nearly got FASTX to a point where it could be released in a BioJulia Registry, I just need to give it one more update to drop some old packages.
    Ciarán O'Mara
    @CiaranOMara
    Nice!
    Ben J. Ward
    @BenJWard
    It should be a good first example and all these new parser packages can follow it, and then I can go and move the stuff we have that is already on METADATA over
    Ciarán O'Mara
    @CiaranOMara
    @BenJWard, have you got the registry working with FASTX?
    Ben J. Ward
    @BenJWard
    @CiaranOMara I've managed to get the registry working for FASTX manually, but we really don't want to work with a registry manually. I'm looking into setting us up Registrator.jl
    Ciarán O'Mara
    @CiaranOMara
    Great stuff re manual registration.
    Ciarán O'Mara
    @CiaranOMara
    I had a quick look at Registrator.jl, I haven’t exhaustively read its code or issues. I’m not sold by the comment based trigger, which appears to address a registry race condition (https://github.com/JuliaComputing/Registrator.jl/issues/1#issuecomment-465863422). I initially thought Registrator.jl didn't use a merged based trigger because many people develop in their master branch, then choose to tag commits in the master branch for release… I guess I haven’t yet worked out the rationale behind the design and why a tag-based trigger (which is more in line with my thinking) is not appropriate.
    Ben J. Ward
    @BenJWard
    I think their thinking is to make the release, and then when the release is made, then tag the commit.
    In order to avoid the situation where you tag a release - attobot rejects, and then you have to delete tags and do it all over again.
    It used to annoy me, but not enough for me to complain about it or do anything different, it was just "how it was".
    I kinda feel the same about this method of doing it too with registrator. I've used tools that work similarly like bors before. I have no over-riding preference.