-
Notifications
You must be signed in to change notification settings - Fork 145
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
documentation for .yeb format #161
Conversation
Did we get the docs for the yeb options anywhere yet? |
What do you mean with yeb options? |
Maybe what I'm looking for is pre-release docs. We could put them somewhere else (ie, checkout feature branch, use --experimental etc). Also, the example in the docs seems to be slightly wrong (easyblock shouldn't be specified, or should be bzip I think, since there is no configure script used for the sources) |
Also the escaping in the docs for Is * a preference or something that makes sense to YAML? It is going to be a bit of a pain long term I imagine (for the same reason the docs are hard to escape). |
We currently don't have documentation for pre-release stuff, but we can add instructions here on how to start playing around with this. |
that might be nice. This is a really cool feature. Definitely looking forward to this moving forward. |
And you're right about the |
Maybe we should create a feature branch of easyconfigs with some interesting examples merged? |
The It's the best we found so far to as equivalent to the |
A feature branch with easyconfigs makes sense to me. Question is how we should organise things there. Do we simply mix |
Yes, I think so about mixing. Though I think we expect to have only one .yeb per software (though we may allow inheritance of some sort) |
easyblock: ConfigureMake | ||
|
||
name: gzip | ||
version: '1.6' # FIXME bug: quotes are required here to make sure this is parsed a a string, not a floating point value |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Caylo: please look into this, make very sure somehow that version
is string after parsing...
It's probably time we define the expected type for each of the easyconfig parameters...
Also, please include this gzip.yeb
in the test easyconfigs, and include it in the tests for .yeb
.
vars: | ||
- &f foo | ||
- &b bar | ||
!join [f, bar] # returns 'foobar' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this works with f
, no *f
required?
a76b54a
to
1b2c95b
Compare
dcfaa21
to
8559ad9
Compare
Add this feature to the list of experimental features in: :ref:`experimental_features |
Useful links: | ||
|
||
* YAML syntax specification: http://www.yaml.org/spec/1.2/spec.html | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is PyYAML a 1.2 parser? They advertise as 1.1 (though I imagine there are some extensions)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, good point.
Although, PyYAML is not complaining when we're using %YAML 1.2
as a header.
Merge it as is, things look fine and generally good. We'll work with it and update as we learn more. |
@rjeschmi: makes sense, let's do that indeed, thanks for the review! |
Compiled version: http://caylo-easybuild.readthedocs.org/en/yeb-docs/Writing_yeb_easyconfig_files.html