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

Add searchable cradle dependencies #42

Merged
merged 8 commits into from
Sep 18, 2019

Conversation

fendor
Copy link
Collaborator

@fendor fendor commented Sep 16, 2019

Extends hie.yaml file format with the "dependencies" object.
Extends Bios cradle type with an optional FilePath to
obtain cradle dependencies from.

Set for each cradle type the cradle dependencies.

Reorganise parsing of "hie.yaml".

  • For each cradle type, implement a function that returns dependencies common to the respective cradle type.
  • Test the parsing of hie.yaml a bit more, smoke testing succeeded

Note: parsing of hie.yaml is less strict now, if there is a field such as "dependecies" (note missing 'n'), it will parse, assuming the correct field "dependencies" is not defined.

Closes #35
Makes #39 obsolete

Extends hie.yaml file format with the "dependencies" object.
Extends Bios cradle type with an optional FilePath to
obtain cradle dependencies.

Set for each cradle type the cradle dependencies.

Reorganise parsing of "hie.yaml".
cradleRootDir = wdir
, cradleOptsProg = CradleAction "obelisk" (obeliskAction wdir)
obeliskCradleDependencies :: FilePath -> IO [FilePath]
obeliskCradleDependencies _wdir = return []
Copy link
Collaborator Author

@fendor fendor Sep 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couldnt find any obelisk files in a very shallow search (mainly the obelisk gh page)

@fendor fendor changed the title WIP: Add searchable cradle dependencies Add searchable cradle dependencies Sep 16, 2019
@mpickering
Copy link
Collaborator

I think just needs a update to the README.

@fendor fendor force-pushed the better-cradle-deps branch 2 times, most recently from cb1a46a to a2a7766 Compare September 16, 2019 20:32
README.md Outdated Show resolved Hide resolved
@mpickering
Copy link
Collaborator

Surely the dependencies field should be at the top level, like cradle? What's your reasoning for the way you have implemented it?

@fendor
Copy link
Collaborator Author

fendor commented Sep 17, 2019

Surely the dependencies field should be at the top level, like cradle? What's your reasoning for the way you have implemented it?

My reasoning was these are the depedencies of a cradle and a cradle specification consists of a type of cradle and dependencies to that cradle.
But no technical reasoning.

@mpickering
Copy link
Collaborator

Can you change the dependencies to be on the top level of the yaml file?

Then I will merge it. The cradle option is really specifying the CradleType.

@mpickering mpickering merged commit c4d7517 into haskell:master Sep 18, 2019
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

Successfully merging this pull request may close these issues.

Report what files are dependencies of the Cradle
2 participants