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

including dockerfiles for MCnet tools? #13

Open
lukasheinrich opened this issue Jan 28, 2016 · 5 comments
Open

including dockerfiles for MCnet tools? #13

lukasheinrich opened this issue Jan 28, 2016 · 5 comments

Comments

@lukasheinrich
Copy link

Hi again,

would you like to build this into a general repository for HEP software tools? I have a couple of Dockerfiles for MCNet tools like Sherpa/Herwig/Madgraph/Rivet and other things like ROOT etc and I'd be happy to contribute.

Cheers,
Lukas

@sbinet
Copy link
Contributor

sbinet commented Jan 28, 2016

sure, send them in. or, rather, PR-them in :)

@lukasheinrich
Copy link
Author

Hi,

so I have this repo:

https://github.com/lukasheinrich/hepsw-docker

would you like to follow a specific scheme on the dockerfiles?

@sbinet
Copy link
Contributor

sbinet commented Feb 4, 2016

looks good.

what do you mean by "follow[ing] a specific scheme on the dockerfiles" ?

  • a standard installation path for the binaries (inside the container) ?
  • a standard installation location for the sources ?
  • a standard location or naming scheme for the Dockerfiles inside the hepsw/docks repository ?

@lukasheinrich
Copy link
Author

yeah possibly any of those. the existing one seem to come with a Dockerfile + a Makefile to do build and push. Also maybe could be a good idea to try to systematically build base layers. E.g I did try to use the slc-dev image for some stuff, but needed to compile gcc4.9 on top.

we can also just let it be free-form, just wanted to ask before I start putting in PRs. At least a naming scheme of directories sounds reasonable

@sbinet
Copy link
Contributor

sbinet commented Feb 5, 2016

ok. let's start with indeed a Dockerfile + Makefile to streamline the build+upload process.

as for the layout of the directories holding these Dockerfiles, I would just start relatively flat (except if you want to put the mcnet related tools under, say, mctools or something.)
we can still git mv stuff around.

for the sources being installed inside the container (if any), I would put them under
/opt/hepsw/<some-name> and install the binaries+headers under /usr/{include,lib,bin}

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

2 participants