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

build/all.py pollutes root folder on Windows #776

Closed
Ross-cz opened this issue May 3, 2017 · 6 comments
Closed

build/all.py pollutes root folder on Windows #776

Ross-cz opened this issue May 3, 2017 · 6 comments
Assignees
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly type: external An issue with an external dependency; not our issue; sometimes kept open for tracking
Milestone

Comments

@Ross-cz
Copy link
Contributor

Ross-cz commented May 3, 2017

  • What version of Shaka Player are you using?
    latest master (bf1c829)

  • What browser and OS are you using?
    Windows, npm 4.5.0

  • What did you do?
    python build/all.py

  • What did you expect to happen?
    git status clean report

  • What actually happened?
    Untracked / unignored files were created:

c:\git\shaka-player-repo>git status
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
  (use "git add <file>..." to include in what will be committed)

        esparse
        esparse.cmd
        esvalidate
        esvalidate.cmd
        htmlhint
        htmlhint.cmd
        in-install
        in-install.cmd
        in-publish
        in-publish.cmd
        karma
        karma.cmd
        not-in-install
        not-in-install.cmd
        not-in-publish
        not-in-publish.cmd
        r.js
        r.js.cmd
        r_js
        r_js.cmd
        rimraf
        rimraf.cmd

nothing added to commit but untracked files present (use "git add" to track)
@joeyparrish joeyparrish added the type: bug Something isn't working correctly label May 3, 2017
@joeyparrish joeyparrish added this to the v2.2.0 milestone May 3, 2017
@joeyparrish
Copy link
Member

This is certainly not intentional. We don't get the same behavior on Linux, but we'll try to reproduce on Windows.

@joeyparrish joeyparrish self-assigned this May 4, 2017
@joeyparrish
Copy link
Member

I tested on Windows 10 with npm 3.10.3, in a clean checkout at rev 0698987.

I find that npm install run manually does not pollute the folder with node bin files.

However, if I wipe out node_modules and run python build/all.py, letting it run npm install for me, I can reproduce the pollution:

$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
  (use "git add <file>..." to include in what will be committed)

        esparse
        esparse.cmd
        esvalidate
        esvalidate.cmd
        htmlhint
        htmlhint.cmd
        in-install
        in-install.cmd
        in-publish
        in-publish.cmd
        karma
        karma.cmd
        not-in-install
        not-in-install.cmd
        not-in-publish
        not-in-publish.cmd
        r.js
        r.js.cmd
        r_js
        r_js.cmd
        rimraf
        rimraf.cmd

nothing added to commit but untracked files present (use "git add" to track)

There must be something we're doing wrong. We'll investigate further.

@joeyparrish joeyparrish removed their assignment May 4, 2017
@Ross-cz
Copy link
Contributor Author

Ross-cz commented May 5, 2017

Thanks Joey. I don't keen on the fix. There is probably some incompatibility with cygwin used by python on the Windows.

Maybe the community can help and rework python scripts to full nodejs project?

@joeyparrish
Copy link
Member

I don't think we're interested in moving the build scripts to nodejs at this time. We use python in our test lab infrastructure, so it is useful for us to be able to import those build scripts as part of our automation.

@joeyparrish joeyparrish self-assigned this Jun 6, 2017
@joeyparrish joeyparrish changed the title Running python build/all.py pollutes root folder by npm ref executables build/all.py pollutes root folder on Windows Jun 6, 2017
@joeyparrish
Copy link
Member

With npm v3.10.3:

npm.cmd update does not pollute the root folder.
npm.cmd --prefix C:/cygwin64/home/user/shaka-player update does pollute the root folder.
npm.cmd --prefix . update does pollute the root folder.

Since npm behaves differently on other platforms, and the behavior is specific to --prefix it seems to be a bug in npm --prefix on Windows.

@joeyparrish joeyparrish added the type: external An issue with an external dependency; not our issue; sometimes kept open for tracking label Jun 6, 2017
@joeyparrish
Copy link
Member

I filed npm/npm#17027 to fix the behavior of --prefix. In the mean time, we may be able to work around it.

joeyparrish added a commit that referenced this issue Jun 15, 2017
Closes #776, #854

Change-Id: I63e785342e051042ba603b63973ddfdc89d80f1a
@shaka-project shaka-project locked and limited conversation to collaborators Mar 22, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly type: external An issue with an external dependency; not our issue; sometimes kept open for tracking
Projects
None yet
Development

No branches or pull requests

3 participants