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

Allow maker2jbrowse to be usable when it exists in $PATH rather than only in bin/maker2jbrowse #877

merged 9 commits into from Jan 29, 2018


None yet
3 participants

cmdcolin commented Mar 29, 2017

The maker2jbrowse automatically runs and, but it assumes those scripts will be located in the current directory + "bin/". This is not necessarily true if you install the perl scripts using "cpanm git://" then they can be installed to a system bin directory

This PR therefore allows the maker2jbrowse script to assume that and can exist in the $PATH

It also has a small rider extension to allow maker2jbrowse to specify --sortMem which can be helpful for large files

Note that other scripts like and have had this support to be installed to system bin directories for awhile

@wafflebot wafflebot bot added the in progress label Jan 29, 2018


This comment has been minimized.


rbuels commented Jan 29, 2018

@cmdcolin There's something not quite right about this, the tests are throwing uninitialized warnings:


@rbuels rbuels added the feature req label Jan 29, 2018

@rbuels rbuels added this to the 1.12.4 milestone Jan 29, 2018


This comment has been minimized.


cmdcolin commented Jan 29, 2018

Thanks for catching that, I think these perl tests should be passing now. It was due to adding --compress argument improperly to the command lines

@rbuels rbuels merged commit 6dee7af into master Jan 29, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
continuous-integration/travis-ci/push The Travis CI build passed

@wafflebot wafflebot bot removed the in progress label Jan 29, 2018

@cmdcolin cmdcolin deleted the new_maker2jbrowse branch Feb 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment