bug#47335: Hide GHC not used for building Was: xmonad fails to recompile on guix system
Hi, On Wed, 15 Sept 2021 at 13:02, Xinglu Chen wrote: > Agreed, but I guess using the ‘-next’ suffix was be the easiest > workaround for now. Yeah but more than often, the workarounds remain longer than expected and thus they cannot be considered as workaround. ;-) > Maybe running ‘guix install ghc’ should install the GHC package that the > ‘ghc’ variable refers to. Then this would not only apply to language > ecosystems, but all packages in general. Right now running ‘guix > install rsync’ installs the ‘rsync-next’ package, but I would expect it > to install the package that the ‘rsync’ variable is bound to. Well, the name has to be distinguished from the symbol. The symbol name does not matter from a CLI point of view; and usually not so much from a regular user perspective. What really matters, IMHO, is the name and the version. Basically, "guix install foo" will install the latest version of the package 'foo'. To avoid this, the trick is to tweak to the name of the latest version. It is what happens with 'rsync'; so to be in agreement with the '-next' approach, the name should be 'rsync-next' and not 'rsync'. Anyway, we all agree that something is odd. :-) Cheers, simon
bug#47335: Hide GHC not used for building Was: xmonad fails to recompile on guix system
On Wed, Sep 15 2021, zimoun wrote: > Hi, > > On Wed, 15 Sept 2021 at 09:43, Lars-Dominik Braun wrote: > >> > I'd be very much in favor of the latter, or maybe rename it to ghc-next. >> > I have some profiles ghc pinned to a version and upgrading those is >> > always a mess because Guix tries to build the old version from source >> > instead of using the next version. >> >> I renamed ghc@8.8 to ghc-next in commit >> 39b43d0d0428474a1d0bf58779d0135163b9c6e3. > > Well, I am late to the party and probably out of point but I think > this '-next' is not something we should introduce and generalize. > Well, who knows if these '-next' will be the real next. ;-) My > comment is also about guile-next, emacs-next and python-next. Noting > that gcc-toolchain does not have a '-next'; packages are built using > 7.5.0 but "guix install gcc-toolchain" will install 11.2.0 and then it > could lead to the same issue as the one reported with GHC, I guess. > > Instead of this '-next' trick, we should find a better mechanism where > "guix install ghc" would install the default GHC used by the Haskell > build-system. Idem for the others guile-next, python-next etc.. And > any other version should be installed using the explicit mention, > i.e., "guix install ghc@8.8", IMHO. Agreed, but I guess using the ‘-next’ suffix was be the easiest workaround for now. Maybe running ‘guix install ghc’ should install the GHC package that the ‘ghc’ variable refers to. Then this would not only apply to language ecosystems, but all packages in general. Right now running ‘guix install rsync’ installs the ‘rsync-next’ package, but I would expect it to install the package that the ‘rsync’ variable is bound to. signature.asc Description: PGP signature
bug#47335: Hide GHC not used for building Was: xmonad fails to recompile on guix system
Hi, On Wed, 15 Sept 2021 at 09:43, Lars-Dominik Braun wrote: > > I'd be very much in favor of the latter, or maybe rename it to ghc-next. > > I have some profiles ghc pinned to a version and upgrading those is > > always a mess because Guix tries to build the old version from source > > instead of using the next version. > > I renamed ghc@8.8 to ghc-next in commit > 39b43d0d0428474a1d0bf58779d0135163b9c6e3. Well, I am late to the party and probably out of point but I think this '-next' is not something we should introduce and generalize. Well, who knows if these '-next' will be the real next. ;-) My comment is also about guile-next, emacs-next and python-next. Noting that gcc-toolchain does not have a '-next'; packages are built using 7.5.0 but "guix install gcc-toolchain" will install 11.2.0 and then it could lead to the same issue as the one reported with GHC, I guess. Instead of this '-next' trick, we should find a better mechanism where "guix install ghc" would install the default GHC used by the Haskell build-system. Idem for the others guile-next, python-next etc.. And any other version should be installed using the explicit mention, i.e., "guix install ghc@8.8", IMHO. Cheers, simon
bug#47335: Hide GHC not used for building Was: xmonad fails to recompile on guix system
Hi, > I'd be very much in favor of the latter, or maybe rename it to ghc-next. > I have some profiles ghc pinned to a version and upgrading those is > always a mess because Guix tries to build the old version from source > instead of using the next version. I renamed ghc@8.8 to ghc-next in commit 39b43d0d0428474a1d0bf58779d0135163b9c6e3. Cheers, Lars
bug#47335: Hide GHC not used for building Was: xmonad fails to recompile on guix system
On Mon, 26 Jul 2021 08:47:53 +0200 Lars-Dominik Braun wrote: > Hi, > > I’m seeing the same issue, but it works when explicitly installing > ghc@8.6. Looking at haskell-build-system all Haskell libraries are > currently built with version 8.6, whereas the newest GHC version > available (and thus installed by `guix install`) is 8.8. > > I feel that either xmonad should depend on the correct GHC or all > GHC versions not used to build libraries should be hidden to avoid > this situation. > > Lars > > > > I'd be very much in favor of the latter, or maybe rename it to ghc-next. I have some profiles ghc pinned to a version and upgrading those is always a mess because Guix tries to build the old version from source instead of using the next version.
