Page MenuHomeFreeBSD

Add deps, fix conflicts/comments.

Authored by xmj on Sep 23 2014, 11:27 AM.
Referenced Files
Unknown Object (File)
May 16 2024, 6:42 AM
Unknown Object (File)
May 16 2024, 6:42 AM
Unknown Object (File)
May 9 2024, 2:46 AM
Unknown Object (File)
Apr 26 2024, 6:58 AM
Unknown Object (File)
Apr 10 2024, 9:55 PM
Unknown Object (File)
Apr 10 2024, 9:55 PM
Unknown Object (File)
Apr 10 2024, 8:39 PM
Unknown Object (File)
Apr 7 2024, 2:53 AM



Add missing dependencies to audio/linux-c6-{flac,libsndfile,alsa-plugins-pulseaudio,pulseaudio-libs} , fix comments and conflicts in flac

Test Plan

builds ok locally, pulling in the right dependencies

Diff Detail

rP FreeBSD ports repository
No Lint Coverage
No Test Coverage

Event Timeline

xmj retitled this revision from to Add deps, fix conflicts/comments..
xmj updated this object.
xmj edited the test plan for this revision. (Show Details)
xmj added reviewers: koobs, swills.


Add missing deps, fix COMMENT/CONFLICTS

Add missing dependencies to audio/linux-c6-{flac,libsndfile,alsa-plugins-pulseaudio,pulseaudio-libs};
set proper COMMENT and CONFLICTS in audio/linux-c6-flac (both of which I missed in r368845).

PR: 193862
Submitted by: Jan Beich <>
Approved by: koobs (mentor)

Since its unclear that you are on emulation@, and a blanket does not apply, make it clear in your commit log you are addressing issues you are introduced, and are tidying up.

A clear and documented reason that there is approval for a commit is always prudent. This may be

  • Blanket stuff
  • Maintainer
  • Implicit (you wear the group@ hat, or are a member)
  • You maintain it
  • There is evidence in a linked issue (and referenced in the commit) that we have approval
koobs edited edge metadata.


This revision is now accepted and ready to land.Sep 23 2014, 11:58 AM

Note that @xmj provided poudriere build logs outside of the review context (on IRC).

Note that test plan section needs to be obvious what QA was completed, and their results. "OK" is fine for each test run if they are successful.

Please also include the proposed shortlog/commit log in the review summary itself (ideally in code blocks), rather than a comment.

This means that all relevant info needed to approve is right up the top

Committed revision 369048.