Skip to content

copy third party notices to module folder at build time #605

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

Conversation

TylerLeonhardt
Copy link
Member

When you build, it will copy the Third Party Notices.txt into the module folder for when we distribute the extension.

I don't really like that the module folder gets checked in to the repro (Any reason why we do that?) since it's generated at build time, but I'm considering that out of scope for now which is why the Third Party Notices is in this PR too.

@daviwil
Copy link
Contributor

daviwil commented Jan 8, 2018

We do it because some of the files there (modules/PowerShellEditorServices/PowerShellEditorServices.ps*) only exist there. You could eventually change it so that this folder gets generated automatically, but I dunno how much extra benefit you'd get out of it.

For now we just add specific entries to .gitignore to avoid having these things checked in. I'd add the Third Party Notices file under modules path to .gitignore:

https://github.com/PowerShell/PowerShellEditorServices/blob/master/.gitignore#L30

@TylerLeonhardt
Copy link
Member Author

Ohhhhhhh that makes a lot of sense then. I didn't realize those weren't generated. Cool!

@TylerLeonhardt TylerLeonhardt merged commit a141b64 into PowerShell:master Jan 8, 2018
@TylerLeonhardt TylerLeonhardt deleted the add-third-party-notices-to-build branch January 8, 2018 20:22
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.

2 participants