Re: port "cask" -- installing prebuilt binaries

On 2020-08-14 11:48 p.m., Lothar Haeger wrote: Am 15.08.2020 um 01:11 schrieb Ken Cunningham : so -- what would a user typing Obviously that variant would conflict with all other variants, much like +ruby21 conflicts with +ruby22. So the user would type sudo port -v install macvim +prebui

Re: port "cask" -- installing prebuilt binaries

On 8/15/20 8:48 , Lothar Haeger wrote: >> Am 15.08.2020 um 01:11 schrieb Ken Cunningham >> : >> >> so -- what would a user typing > Obviously that variant would conflict with all other variants, much like > +ruby21 conflicts with +ruby22. So the user would type > > sudo port -v install macvim +p

Re: port "cask" -- installing prebuilt binaries

> Am 15.08.2020 um 09:47 schrieb Eric F (iEFdev) : > > Doesn't the port `ghc` do exactly this? > https://github.com/macports/macports-ports/blob/master/lang/ghc/Portfile#L31-L33 > > Yes, looks like it does. Thr

Re: port "cask" -- installing prebuilt binaries

Doesn't the port `ghc` do exactly this? https://github.com/macports/macports-ports/blob/master/lang/ghc/Portfile#L31-L33 The variant name is: +prebuilt throwaway bootstrap compiler only, totally different issue

Writing useful comments in Portfiles

Most Portfiles don't need any comments. We especially want to avoid comments that do nothing but state what the code is doing; such comments are counterproductive because they force the reader to read more without giving them more information, and such comments can also easily get out of sync wi