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

cmd/vendor/golang.org/x/sys/unix: chase FreeBSD header rename #28742

Closed
wants to merge 1 commit into from

Conversation

emaste
Copy link

@emaste emaste commented Nov 12, 2018

When Capsicum (FreeBSD's capability-based sandboxing framework) was
first developed it used sys/capability.h as its header, but that
conflicted with the draft POSIX.1e capability header used on other
systems (Linux). As a result FreeBSD's header was renamed to
sys/capsicum.h, with capability.h remaining as a backwards-compatibility
shim.

Today all supported (and most unsupported) versions of FreeBSD have
sys/capsicum.h so unconditionally switch to using the updated header.

When Capsicum (FreeBSD's capability-based sandboxing framework) was
first developed it used sys/capability.h as its header, but that
conflicted with the draft POSIX.1e capability header used on other
systems (Linux).  As a result FreeBSD's header was renamed to
sys/capsicum.h, with capability.h remaining as a backwards-compatibility
shim.

Today all supported (and most unsupported) versions of FreeBSD now have
sys/capsicum.h so unconditionally switch to using the updated header.
@googlebot googlebot added the cla: yes Used by googlebot to label PRs as having a valid CLA. The text of this label should not change. label Nov 12, 2018
@gopherbot
Copy link

This PR (HEAD: 06cc0b5) has been imported to Gerrit for code review.

Please visit https://go-review.googlesource.com/c/go/+/148836 to see it.

Tip: You can toggle comments from me using the comments slash command (e.g. /comments off)
See the Wiki page for more info

@gopherbot
Copy link

Message from Gobot Gobot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
Within the next week or so, a maintainer will review your change and provide
feedback. See https://golang.org/doc/contribute.html#review for more info and
tips to get your patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11, it means that this CL will be reviewed as part of the next development
cycle. See https://golang.org/s/release for more details.


Please don’t reply on this GitHub thread. Visit golang.org/cl/148836.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Brad Fitzpatrick:

Patch Set 1: Code-Review-2

We don't modify things in vendor/* directories manually. You have to fix it upstream first, and then we'll update the copy here later.


Please don’t reply on this GitHub thread. Visit golang.org/cl/148836.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Ed Maste:

Patch Set 1:

Patch Set 1: Code-Review-2

We don't modify things in vendor/* directories manually. You have to fix it upstream first, and then we'll update the copy here later.

Would you kindly let me know how to find the upstream for this?


Please don’t reply on this GitHub thread. Visit golang.org/cl/148836.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Ian Lance Taylor:

Patch Set 1:

We don't modify things in vendor/* directories manually. You have to fix it upstream first, and then we'll update the copy here later.

Would you kindly let me know how to find the upstream for this?

It's the package golang.org/x/sys/unix.

I think this problem is already fixed upstream, actually. If so we just need to vendor in a new version.


Please don’t reply on this GitHub thread. Visit golang.org/cl/148836.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

Message from Ed Maste:

Patch Set 1:

I think this problem is already fixed upstream, actually. If so we just need to vendor in a new version.

Indeed, it was fixed in 3a27cdc.


Please don’t reply on this GitHub thread. Visit golang.org/cl/148836.
After addressing review feedback, remember to publish your drafts!

@gopherbot
Copy link

This PR is being closed because golang.org/cl/148836 has been abandoned.

@gopherbot gopherbot closed this Nov 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Used by googlebot to label PRs as having a valid CLA. The text of this label should not change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants