Re: git: 81a047b386e5 - main - www/*chromium: drop pulseaudio build dependency by using an internal copy

On 25/06/24 14:24 GMT, Vladimir Druzenko wrote:
> 30.05.2024 19:25, Sergey A. Osokin пишет:
> > On Thu, May 30, 2024 at 03:15:53PM +0300, Vladimir Druzenko wrote:
> > > 28.05.2024 09:26, Gleb Popov пишет:
> > > > On Mon, May 27, 2024 at 6:56 PM Vladimir Druzenko <vvd@freebsd.org> wrote:
> > > > > Just return all options.
> > > > It is unrealistic to ask for removing Pulseaudio from default options
> > > > as it is already default in many other ports. Robert gone an extra
> > > > mile for you to make this dependency build-time rather than runtime.
> > > > 
> > > > Start using Poudriere to build your own set of packages with options
> > > > you want rather than going against the stream and putting more work on
> > > > others.
> > > > 
> > > > P.S. Your work on Chromium stuff is greatly appreciated, rnagy@
> > > > P.S.S I wouldn't even bother to use bundled copy of pulseaudio libs if
> > > > that adds more patches
> > > You ignored main part:
> > > 
> > > One of my installation of this port is on headless VM (2 VMs) for export
> > > Draw.io diagrams to PDF. I don't need any sound on this VM.
> > > Instead of leaving options in the port (what could be simpler?), each time
> > > the port is updated, I will have to manually remove unnecessary
> > > dependencies, add "GN_ARGS+=use_pulseaudio=false use_sndio=false" and add
> > > option ALSA (for desktop ON, but for VM OFF).
> > > 
> > > How I can build this port without dependency from all sound engines - alsa,
> > > sndio and pulse for install it on headless VM?
> > > Options was the solution! I don't understand who they were bothering?
> > The www/chromium port is broken these days, just because several previously
> > work well online web applications, such as zoom, slack, etc., don't work
> > anymore.
> > 
> > I'd recommend to revert back all *audio*-related changes have been made to
> > restore needful basic functionality.
> > 
> > Thank you.
> 
> Hello!
> 
> Are we planning to enter the 2024Q3with broken *chromium?

What is broken exactly? If someone can get me a proper list of packages installed
and a complete description of the environment I can actually start looking into it.