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

Another attempt to add license file to CRAN recipes. #3284

Merged
merged 3 commits into from
Dec 10, 2018

Conversation

jdblischak
Copy link
Contributor

Now that the installation path for R is the same across all operating systems (conda-forge/r-base-feedstock#61), I am resubmitting an updated version of my previous PR (#2831) to add the license file to recipes of R packages that use the standard licenses shipped with R base.

Here are some examples:

  • usethis - GPL-3 (specifically License: GPL-3)
    • license_file: '{{ environ["PREFIX"] }}/lib/R/share/licenses/GPL-3'
  • abf2 - Artistic-2.0 (specifically License: Artistic-2.0)
    • license_file: '{{ environ["PREFIX"] }}/lib/R/share/licenses/Artistic-2.0'
  • corTools - Artistic-2.0 (specifically License: Artistic License 2.0)
    • license_file: '{{ environ["PREFIX"] }}/lib/R/share/licenses/Artistic-2.0'
  • Ruchardet: Mozilla Public License (specifically License: MPL)
    • r-base does not ship the MPL license, so there is no license_file line added

I'd like to convert these examples into unit tests. I'm guessing that the appropriate location to add them is in https://github.com/conda/conda-build/blob/master/tests/test_api_skeleton.py, but I'd appreciate some guidance on how best to proceed with structuring the tests before I attempt this.

cc: @msarahan @mingwandroid @isuruf @bgruening
xref: #2831, #2835, conda-forge/staged-recipes#3234, conda-forge/r-base-feedstock#61

@msarahan
Copy link
Contributor

Yep, tests should probably go into test_api_skeleton.py. I don't understand your question about structure, though. Maybe I'll just point out the fixtures in https://github.com/conda/conda-build/blob/master/tests/conftest.py - these are what you'll see most often as inputs to test functions, and they help set up default configs and such. There's also testing_workdir for having a temporary work folder. If you use testing_config, it implicitly uses testing_workdir and you don't need to add testing_workdir also.

@msarahan
Copy link
Contributor

msarahan commented Dec 6, 2018

Let me know if you need further guidance on tests. I'm fine with this PR - just waiting on you to comment on tests.

@jdblischak
Copy link
Contributor Author

Let me know if you need further guidance on tests. I'm fine with this PR - just waiting on you to comment on tests.

@msarahan Thanks. I'll give it a try and let you know if I have any specific questions.

@jdblischak
Copy link
Contributor Author

@msarahan I converted my examples to tests. They pass locally. Please let me know if you'd like me to make any changes.

@msarahan
Copy link
Contributor

Yep, all looks good to me. Thanks!

@github-actions
Copy link

Hi there, thank you for your contribution!

This pull request has been automatically locked because it has not had recent activity after being closed.

Please open a new issue or pull request if needed.

Thanks!

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Apr 17, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants