Re: Install from HEAD instead current stable version?
Clemens Lang writes: > On Thu, Jul 04, 2013 at 11:10:33AM +0200, Rainer M Krug wrote: >> So then I would have to install grass as usual via >> , >> | port install grass >> ` > > Yes. > >> and then upgrade it and specify to use HEAD to fetch - how can I do >> this? > > MacPorts has no way to do this from the command line like homebrew does. > You need to have a Portfile that explicitly specifies what to download > (where you can put in git HEAD, if you want). > > Since such a Portfile will not be accepted into the main port tree, you > need to have a local portfile repository (as described in [1]), where > you can put this modified Portfile for MacPorts to pick up. > > The guide also has all the information on how to fetch from git [2]. > > [1] https://guide.macports.org/#development.local-repositories > [2] https://guide.macports.org/#reference.phases.fetch.git OK - understood. Thanks a lot, Rainer > > HTH, -- Rainer M. Krug email: RMKruggmailcom ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Install from HEAD instead current stable version?
On Thu, Jul 04, 2013 at 11:10:33AM +0200, Rainer M Krug wrote: > So then I would have to install grass as usual via > , > | port install grass > ` Yes. > and then upgrade it and specify to use HEAD to fetch - how can I do > this? MacPorts has no way to do this from the command line like homebrew does. You need to have a Portfile that explicitly specifies what to download (where you can put in git HEAD, if you want). Since such a Portfile will not be accepted into the main port tree, you need to have a local portfile repository (as described in [1]), where you can put this modified Portfile for MacPorts to pick up. The guide also has all the information on how to fetch from git [2]. [1] https://guide.macports.org/#development.local-repositories [2] https://guide.macports.org/#reference.phases.fetch.git HTH, -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Install from HEAD instead current stable version?
Clemens Lang writes: > Hi, > > On Thu, Jul 04, 2013 at 10:08:01AM +0200, Rainer M Krug wrote: >> I am looking for an easy way of installing the development version >> (HEAD) of grass. >> >> under homebrew, I can simply say >> >> , >> | brew install grass --HEAD >> ` >> >> to instal the development version instead of the stable one - is there >> something similar in port? > > MacPorts deliberately does not support this; there are no metrics to > find out when to consider such a port outdated and the build does not > yield reproducible results. If you need this, create a local portfile > repository, copy the grass Portfile to this tree, modify it to fetch > from current git head and change the commitish whenever you need a new > version. You'll probably have to add a artificial version number (like a > date) to get port to recognize that grass has been updated, since git > commits aren't monotonic. OK - thanks for the info. > > BTW: MacPorts will not stop you from specifying HEAD or master as git > commit to fetch. You can use sudo port upgrade --force grass to build a > new version then. So then I would have to install grass as usual via , | port install grass ` and then upgrade it and specify to use HEAD to fetch - how can I do this? Rainer -- Rainer M. Krug email: RMKruggmailcom ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Install from HEAD instead current stable version?
Hi, On Thu, Jul 04, 2013 at 10:08:01AM +0200, Rainer M Krug wrote: > I am looking for an easy way of installing the development version > (HEAD) of grass. > > under homebrew, I can simply say > > , > | brew install grass --HEAD > ` > > to instal the development version instead of the stable one - is there > something similar in port? MacPorts deliberately does not support this; there are no metrics to find out when to consider such a port outdated and the build does not yield reproducible results. If you need this, create a local portfile repository, copy the grass Portfile to this tree, modify it to fetch from current git head and change the commitish whenever you need a new version. You'll probably have to add a artificial version number (like a date) to get port to recognize that grass has been updated, since git commits aren't monotonic. BTW: MacPorts will not stop you from specifying HEAD or master as git commit to fetch. You can use sudo port upgrade --force grass to build a new version then. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
