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

Bower: Ignore development and documentation files on bower.json. Fix #10313 #10353

Merged
merged 2 commits into from
Nov 14, 2013
Merged

Bower: Ignore development and documentation files on bower.json. Fix #10313 #10353

merged 2 commits into from
Nov 14, 2013

Conversation

rwillrich
Copy link
Contributor

Fixes #10313.

I've kept only the files I consider relevant to bower installation:

  • Files in dist directory;
  • Files in js directory;
  • Files in less directory;
  • bower.json file;
  • README.md file;
  • LICENSE file.

…10313.

I've kept only the files I consider relevant to bower installation:

- Files in dist directory;
- Files in js directory;
- Files in less directory;
- bower.json file;
- README.md file;
- LICENSE file.
"_*",
"assets",
"examples",
"/fonts",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does only this entry have a leading slash?

@rwillrich
Copy link
Contributor Author

It's because it should match only the top fonts directory, and not the fonts directory inside dist.

@kevinSuttle
Copy link

This is still an active issue btw. Looks like it's just cloning the whole repo instead of just the relevant parts.

@rwillrich
Copy link
Contributor Author

@cvrebert Any chances that this PR be merged on master?

"**/.*"
"**/.*",
"_*",
"assets",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should now be docs-assets.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll revise and made this modification.

@cvrebert
Copy link
Collaborator

I'm not personally going to be the one to merge it since I'm not a Bower expert.
/cc Bower-meister @fat

@rwillrich
Copy link
Contributor Author

@fat @cvrebert Any chance of this going to production?

@Ninir
Copy link
Contributor

Ninir commented Nov 14, 2013

👍 This one is still an important step. Getting the project through bower leads to polluting files...
@fat Any chance you get a look at this one please?

@rwillrich
Copy link
Contributor Author

@Ninir +1

cvrebert added a commit that referenced this pull request Nov 14, 2013
Bower: Ignore development and documentation files on bower.json. Fix #10313
@cvrebert cvrebert merged commit 57b59fc into twbs:master Nov 14, 2013
@cvrebert
Copy link
Collaborator

Oh, whatever. Looks sensible. :shipit:

@rwillrich rwillrich deleted the ignore-files branch November 14, 2013 23:48
@rwillrich rwillrich restored the ignore-files branch November 14, 2013 23:48
@rwillrich rwillrich deleted the ignore-files branch November 14, 2013 23:48
@Ninir
Copy link
Contributor

Ninir commented Nov 15, 2013

THanks @cvrebert, you're the man :) 👍

@mdo mdo mentioned this pull request Nov 16, 2013
@sebdavid
Copy link

Damned, I just see this point after the new 3.0.3 is released...

Hi guys,

I'm installing bootstrap via bower, through grunt (with grunt-bower-task). Then, post install actions are run via grunt-bower-postinst. Concerning bootstrap, these actions are : running 'npm' command, override and copy some bootstrap .less files to customize the theme, and finally running 'grunt dist-css'. Now that config files are ignored when installing bootstrap (package.json, Gruntfile.js), it doesn't work anymore (with 3.0.3).

I'm sure I can modify my process to compile bootstrap .less files in an other way, but it would be easier to re-use the task defined in bootstrap's Gruntfile. This way allows to use the original task configuration too. It seems odd that .less files are installed, but not the tools to compile them.

I'm ok with the idea to not install documentation files (.html, ...), node_modules folder, etc. But what about config files ? Why should it not be installed ? The aim is not to install the component as in a production environment.

Thank you in advance for your answers.

@cvrebert
Copy link
Collaborator

@sebdavid See #11780.

@sebdavid
Copy link

ok, great, thank you.
I'll get the gruntfile manually in waiting 3.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why does Bower installation download the entire Bootstrap repo?
6 participants