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

.git directory is deleted #2360

Closed
jakirkham opened this issue Sep 12, 2017 · 3 comments
Closed

.git directory is deleted #2360

jakirkham opened this issue Sep 12, 2017 · 3 comments
Labels
locked [bot] locked due to inactivity stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity

Comments

@jakirkham
Copy link
Member

Appears that .git directories added to the $PREFIX during the build are stripped out entirely by conda-build. However not all . prefixed files are stripped. This is undesirable behavior if one wants to have a git repo in their package. A recipe that demonstrates this behavior is included in the details below. Ran this on macOS, but presumably it shows up everywhere.

# filename: test-recipe/meta.yaml

package:
  name: test-recipe
  version: 1

build:
  script: git clone https://github.com/jakirkham/hello_tests "${PREFIX}/hello_tests"

requirements:
  build:
    - git

test:
  requires:
    - git

  commands:
    - cd "${PREFIX}/hello_tests"
    - git status
@jakirkham jakirkham changed the title .git repo is deleted? .git directory is deleted? Sep 12, 2017
@jakirkham jakirkham changed the title .git directory is deleted? .git directory is deleted Sep 12, 2017
@t-bltg
Copy link

t-bltg commented Sep 15, 2017

You can easily change the .git pattern in conda build ?

https://github.com/conda/conda-build/blob/master/conda_build/utils.py#L1000

@jakirkham
Copy link
Member Author

Sorry I'm unclear. Are you saying there is a meta.yaml setting to override this? Or merely suggesting conda-build can be fixed? Would agree with the latter (though it doesn't change my current predicament), but the former would be interesting to know.

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Aug 28, 2022
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Sep 27, 2022
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Sep 27, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity
Projects
None yet
Development

No branches or pull requests

2 participants