maintainer-feedback requested: [Bug 289243] security/libsecret: sometimes fails if older libsecret installed

Bugzilla Automation <[email protected]> has asked freebsd-gnome (Nobody)
<[email protected]> for maintainer-feedback:
Bug 289243: security/libsecret: sometimes fails if older libsecret installed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289243



--- Description ---
Sometimes, security/libsecret can fail is an older libsecret is installed which
may conflict with a newer libsecret in some way.  It is often desirable for
developers to be able to build with newer source code even while an older
libsecret is concurrently installed in the main system path (${LOCALBASE}/...)
and being used for applications while doing development on the latest
libsecret.

One fix is to get the libsecret build to look in the local source tree first
for its own files.

Here is an example of a failure building libsecret-0.21.7 while
libsecret-0.20.5 is installed in ${LOCALBASE}...

valac -C --pkg gio-2.0 --pkg glib-2.0 --pkg gio-unix-2.0 --pkg gio-2.0
--target-glib 2.44 --pkg glib-2.0 --color=never --directory
libsecret/test-vala-lang.p --basedir ../libsecret libsecret/libsecret-1.vapi
libsecret/mock-service-0.vapi ../libsecret/test-vala-lang.vala
../libsecret/test-vala-lang.vala:22.18-22.43: error:
`Secret.attributes_validate' is not available in libsecret-1 0.20.5. Use
libsecret-1 >= 0.21.2
   22 |     bool valid = Secret.attributes_validate (schema, attributes);
      | 		 ^~~~~~~~~~~~~~~~~~~~~~~~~~
Compilation failed: 1 error(s), 0 warning(s)