I think you have multiple packages with the same name and version, but different supported systems. Am I right?
If that is the case, then guix will select a package based on the specification you give it, so if you give a name, it will select the package with that name and the highest version available. If multiple packages match this criteria, one is selected arbitrarily. Now, supported-systems does not mean "remove this package on other architectures", but rather "can't build this on other architectures". So it's perfectly possible that guix will arbitrarily select a package for a different architecture. I can see two solutions: as you mentionned, get source depending on architecture, that way the other architecture packages are not defined. Another possibility is to append say -x86_64 to the package name. Does it make sense? Le 14 janvier 2023 20:33:13 GMT+01:00, phodina via <[email protected]> a écrit : >Hello, > >I have recently uncovered a "feature" that works little bit than described in >the manual, > >During definition of a new variable, package, there is an option called >supported-systems which defaults to %default-systems. > >However, if the package is known to work on certain architecture the right >thing is to list the supported architectures, right? > >If I select package which is not supported by my current architecture and >build it I get notification like this one: >`warning: package [email protected] does not support x86_64-linux` > >So suppose I have the same package for different architectures, each has it's >own unique tarball. > >I've defined one package and inherited from it, changing the source for the >other and selecting the correct supported-systems. >Unfortunately, this approach fails as Guix does not select the right package I >want to use on the current system. > >So should the approach be to define just one variable for the package and then >conditionally select the right tarball/git for the package? > >Also is this considered bug or a feature? > >FIY I know the right way would be to build Grafana from source in this case >which would solve the issue I just wanted to know in general more about the >use case of the supported-systems option. > >---- >Petr
