Skip to content

Don't un-exclude an excluded package#6338

Closed
darkfeline wants to merge 1 commit into
syl20bnr:developfrom
darkfeline:fix-exclude-override
Closed

Don't un-exclude an excluded package#6338
darkfeline wants to merge 1 commit into
syl20bnr:developfrom
darkfeline:fix-exclude-override

Conversation

@darkfeline

Copy link
Copy Markdown
Contributor

If a layer using a package is loaded after a layer excluding it, the
exclude flag should not be overwritten.

@darkfeline

Copy link
Copy Markdown
Contributor Author

Should the tests be fixed, or should I approach this bug from a different direction?

@TheBB TheBB added the Core label Jun 15, 2016
@darkfeline darkfeline force-pushed the fix-exclude-override branch 3 times, most recently from 756a2ef to 19a786e Compare June 23, 2016 23:18
If a layer using a package is loaded after a layer excluding it, the
exclude flag should not be overwritten.
@darkfeline darkfeline force-pushed the fix-exclude-override branch from 19a786e to f9c2190 Compare July 1, 2016 02:55
@syl20bnr syl20bnr self-assigned this Jul 4, 2016
@syl20bnr

syl20bnr commented Jul 5, 2016

Copy link
Copy Markdown
Owner

Thank you ! 💯
I fixed the tests and made them more granular in: 8549437
Cherry-picked into develop branch, you can safely delete your branch.

@syl20bnr

syl20bnr commented Jul 5, 2016

Copy link
Copy Markdown
Owner

Seems that is was the 3000th closed commit so you get the 3000th closed PR achievement!

@darkfeline darkfeline deleted the fix-exclude-override branch July 5, 2016 06:57
@aaronjensen

Copy link
Copy Markdown
Contributor

This prevents explicitly including packages that have been excluded like evil-terminal-cursor-changer

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.

4 participants