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

create easybuild-experimental repository to host auto-generated easyconfig files #222

Closed
boegel opened this issue Aug 30, 2012 · 5 comments
Assignees
Milestone

Comments

@boegel
Copy link
Member

boegel commented Aug 30, 2012

We should set up an easybuild-experimental repository for hosting auto-generated easyconfig files, and potentially also easyblocks.

These could be generated from other build tools, e.g., pkgsrc, ports, portage, ...

This repository could then serve as a starting point for adding support for software that's already supported somewhere else. The auto-generated easyconfigs/blocks would still need human verification, e.g. adding sanity checks and validation installation correctness, before they are pushed to the main EasyBuild repository.

@ghost ghost assigned fgeorgatos Aug 30, 2012
@fgeorgatos
Copy link
Collaborator

Hi there,

this already exists for some time, I still have to migrate some more of my own work in there:
https://github.com/fgeorgatos/easybuild.experimental # avoided "-"character since I'm not 100% sure it's OK on github

Perhaps I will insert in it some structure from the product:
{pkgsrc, portage, ports, macports, deb, rpm, rpmspec} x {alpha, beta, release}

Where the quality levels roughly correspond to:

  • alpha - automatically made, very crude compilation mode, let's just hope it works - 1% success rate is, er, success
  • beta - it worked once, sometime, somewhere (probably pick them from ebrepo, assuming these contain download checksums and/or signatures, ref. add support for checking checksum of source files #214 & check signatures if available #143)
  • release - human has intervened to screen for obvious errors and shortcomings - anyhow use at own risk

Note:
this gradual approach still is not fully Quality Assured (esp. compiler toolchains/options can make a good difference)

I recommend you supply your comments and close this issue.

@boegel
Copy link
Member Author

boegel commented Aug 31, 2012

Your proposal with alpha/beta/release subdirectories and additional structure for sources looks great to me.

Once you've set it up like you propose, can you write up a wiki page that we can thrown on the EasyBuild main wiki?

We needs this to be documented if we ever want people to use it.
It should mention what the purpose is of this repository, how the easyconfigs that are available there are generated, and how they should be used.

@fgeorgatos
Copy link
Collaborator

Hi pals,

I consider this one resolved, copy-paste (any subset of) documentation from:
https://github.com/fgeorgatos/easybuild.experimental
or
https://github.com/fgeorgatos/easybuild.experimental/wiki

If you feel something is missing, let it be said and I'll check on it.

tia,
Fotis

@fgeorgatos
Copy link
Collaborator

Please close this.

@boegel
Copy link
Member Author

boegel commented Nov 20, 2012

Pointer to the easybuild.experimental wiki is on the EasyBuild wiki at https://github.com/hpcugent/easybuild/wiki/Experimental-repo .

@boegel boegel closed this as completed Nov 20, 2012
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

2 participants