A package picks up a non-master package - bug or intentional?

[ng0 <contact.ng0@cryptolab.net>]

Hi,

I just picked up gnunet-fuse again and the build behaves strange.

You have to know that I keep multiple versions of gnunet and related
packages in my GUIX_PACKAGE_PATH.
Normally I would expect that this:

+    (arguments
+     `(#:configure-flags
+       (list (string-append "--with-gnunet="
+                            (assoc-ref %build-inputs "gnunet")))))

just picks up the gnunet from within the master tree the package
definition itself is in.
But as I recently have build "gnunetgf-0.10.17731daf5" this is being
picked up instead as you can see here:

checking fuse.h usability... yes
checking fuse.h presence... yes
checking for fuse.h... yes
checking for GNUnet core... /gnu/store/xbvcn8fqp5l45dh5s32nmqmvbykahq7k-gnunetgf-0.10.17731daf5
checking for GNUnet util library in /gnu/store/xbvcn8fqp5l45dh5s32nmqmvbykahq7k-gnunetgf-0.10.17731daf5... checking for gnunet/gnunet_util_lib.h... no
configure: error: gnunet-fuse requires GNUnet
phase `configure' failed after 2.8 seconds


I wonder.. why? Is Guix just not clever enough and picks the first
fitting "gnunet" it finds and if already available its store path?

I need to build this with exactly 0.10.1 and not HEAD. HEAD of -fuse
would require HEAD of (gnunet) core, this is why this build fails.
-- 
ng0 -- https://www.inventati.org/patternsinthechaos/