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

[SCM] Recipe with sources in the same repo copies to the source folder gitignored files #3039

Closed
Minimonium opened this issue Jun 13, 2018 · 11 comments
Assignees
Milestone

Comments

@Minimonium
Copy link
Contributor

Situation:
I have a conanfile.py in a repo with:

scm = {
        "type": "git",
        "subfolder": "asdio",
        "url": "auto",
        "revision": "auto"
    }

There are some gitignored files such as .vs.

Problem:
When using conan install -pr=... it uploads everything including ignored files to the source folder.

@memsharded
Copy link
Member

Just to make sure, you mean it copies files to the source folder, don't you? Those files are not uploaded to any server.

@Minimonium
Copy link
Contributor Author

Yep!

@memsharded
Copy link
Member

Then it is not a big issue, is it? It is just a temporary copy, it is not packaged, it is not uploaded. Copying files or folders like .vs shouldn't have any effect.

@Minimonium
Copy link
Contributor Author

Yes, the minor one. It could matter if such temporary files are big, I guess?

@Minimonium
Copy link
Contributor Author

Oh, I forgot. Since .vs is not ignored it blocks conan install if VS is open, @memsharded ! Still a minor one, but anyway.

@lasote lasote changed the title [SCM] Recipe with sources in the same repo uploads to the source folder gitignored files [SCM] Recipe with sources in the same repo copies to the source folder gitignored files Jun 14, 2018
@Minimonium
Copy link
Contributor Author

@memsharded And I assume here that because of that it's pretty easy to get invalid binaries in cases when we're using "revision": "auto", since we could get different binaries in case of yet to be commited changes. Should it clone at source stage then instead of copying everything? I'm missing something here.

@lasote
Copy link
Contributor

lasote commented Jun 18, 2018

we could get different binaries in case of yet to be commited changes.

I think this is the reason we decided to not clone but copy the sources, while you are developing your library you probably don't want to commit any change to be able to try the conan package and see if your entire project works.

@lasote
Copy link
Contributor

lasote commented Jun 20, 2018

I will try to get from git the ignored file list to be applied to the copy.

@lasote lasote added this to the 1.5 milestone Jun 20, 2018
@Minimonium
Copy link
Contributor Author

Right. So we would get all changes (not committed yet) but without ignored stuff? Would be good, thanks!

@lasote lasote mentioned this issue Jun 21, 2018
1 task
@ghost ghost assigned lasote Jun 21, 2018
@ghost ghost added the stage: review label Jun 21, 2018
@ghost ghost removed the stage: review label Jun 26, 2018
@Minimonium
Copy link
Contributor Author

@lasote I'm afraid there is a problem with that feature. It does ignore files, but not folders.

@lasote lasote modified the milestones: 1.5, 1.7 Jul 23, 2018
@lasote lasote reopened this Jul 23, 2018
@lasote
Copy link
Contributor

lasote commented Jul 23, 2018

I will review it. Thanks for reporting.

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

3 participants