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

document working with multiple easyblocks repos #119

Closed
boegel opened this issue Aug 20, 2012 · 6 comments
Closed

document working with multiple easyblocks repos #119

boegel opened this issue Aug 20, 2012 · 6 comments
Milestone

Comments

@boegel
Copy link
Member

boegel commented Aug 20, 2012

(old internal ticket 215)

A contributor should preferably clone the main EasyBuild GitHub repository, implement easyblocks in there and then contribute them back (see also [[Contributing back]]).

If for some reason easyblocks can not be contributed back, they can also be kept in a private easyblocks repository.

Basically, you just need to make sure these private repositories are in the PYTHONPATH, and everything should work out fine.

@claczny
Copy link

claczny commented Nov 29, 2012

I would also like to see a step-wise description. Thank you.

@JensTimmerman
Copy link
Contributor

This is documented a little bit in the FAQ: I don't like the a-z/ directory structure, can I change it?

@boegel
Copy link
Member Author

boegel commented Dec 5, 2012

I created a wiki page that explains this in detail, see https://github.com/hpcugent/easybuild/wiki/Setting-up-your-own-easyblocks-repository .

@claczny: Can you review this? If you think it's OK, we'll close this issue.

@boegel
Copy link
Member Author

boegel commented Dec 5, 2012

I also removed the entry in the FAQ, since it was not entirely correct: you can't use subdirectories in your own easyblocks repo, because there's no way to flatten the namespace twice (as mentioned on the wiki page).

@JensTimmerman
Copy link
Contributor

Well, it might be possible with some dirty hack. I haven't gotten to the bottom of it yet, and our current flattening is already kind of a dirty hack, I don't want to make it any more dirty...

@fgeorgatos
Copy link
Collaborator

Hi folks,

we've been using these instructions since last week with no apparent problem;
I think this can now be closed.

@boegel boegel closed this as completed Jan 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants