-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
sort OptionalObsoleteFiles blocks #896
Conversation
A quick look suggests this is sane. |
Using sort(1) order makes verification of the sort easier.
Presumably these were under MK_CDDL at some point, but these days src.opts.mk takes care of setting them to "no" when MK_CDDL is.
These used to be grouped with MK_GCOV option or the like.
Options should be in sort order by primary option (usually, but not always first in the if statement).
f2d1844
to
0ded3b0
Compare
I've added a comment to document the order (it's unfortunately awkward to enforce mechnically). |
OLD_FILES+=usr/share/examples/dma/mailer.conf | ||
OLD_DIRS+=usr/share/examples/dma | ||
|
||
.if ${MK_DMAGENT} == no |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happened here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The old file doesn't have superfluous whitespace, and the new one doesn't seem to have either...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really don't know what's going on here. There aren't any changes to these DMA lines, but git insists on displaying things this way.
Using sort(1) order makes verification of the sort easier. Reviewed by: emaste, imp, netchild Pull Request: #896
Reviewed by: emaste, imp, netchild Pull Request: #896
Presumably these were under MK_CDDL at some point, but these days src.opts.mk takes care of setting them to "no" when MK_CDDL is. Reviewed by: emaste, imp, netchild Pull Request: #896
Reviewed by: emaste, imp, netchild Pull Request: #896
These used to be grouped with MK_GCOV option or the like. Reviewed by: emaste, imp, netchild Pull Request: #896
Reviewed by: emaste, imp, netchild Pull Request: #896
Reviewed by: emaste, imp, netchild Pull Request: #896
Options should be in sort(1) order by primary option (usually, but not always, first in the if statement). Reviewed by: emaste, imp, netchild Pull Request: #896
Using sort(1) order makes verification of the sort easier. Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
Presumably these were under MK_CDDL at some point, but these days src.opts.mk takes care of setting them to "no" when MK_CDDL is. Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
These used to be grouped with MK_GCOV option or the like. Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
Options should be in sort(1) order by primary option (usually, but not always, first in the if statement). Reviewed by: emaste, imp, netchild Pull Request: freebsd/freebsd-src#896
OptionalObsoleteFiles.inc was almost, but not quite sorted which made it hard to figure out where to put things. There seems to have been a mix of more sorting errors, things that didn't move when the option controlling them changed, and odd choices for locations.
I've broken this up into a set of commits moving one or two blocks at a time in hopes that if people have merge difficulty they will be able to merge individual changes where it's easy to see what the conflict is.