Date: Mon, 8 Apr 2024 22:44:19 +0300 From: Gleb Popov <arrowd@freebsd.org> To: Yuri Victorovich <yuri@freebsd.org> Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: d8f39032884a - main - audio/cardinal: Fix build by adding the LIBLO option Message-ID: <CALH631=nFEbjYqvD3ham9z9A-cu3QARJZ=WqxRJsoRsg1-=ESg@mail.gmail.com> In-Reply-To: <202404081918.438JIlZq012983@gitrepo.freebsd.org> References: <202404081918.438JIlZq012983@gitrepo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 8, 2024 at 10:18=E2=80=AFPM Yuri Victorovich <yuri@freebsd.org>= wrote: > > The branch main has been updated by yuri: > +LIBLO_DESC=3D Build with liblo Quoting Porter Handbook: When describing options, view it from the perspective of the user: "What functionality does it change?" and "Why would I want to enable this?" Do not just repeat the name. For example, describing the NLS option as "include NLS support" does not help the user, who can already see the option name but may not know what it means. Describing it as "Native Language Support via gettext utilities" is much more helpful. I have no idea what liblo is and what it offers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631=nFEbjYqvD3ham9z9A-cu3QARJZ=WqxRJsoRsg1-=ESg>