Re: What is the correct process to pull in a fix?

gt; Cool that nice and simple. Barry > On 14 Oct 2017, at 10:41 am, Barry Scott <ba...@barrys-emacs.org > <mailto:ba...@barrys-emacs.org>> wrote: > >> #55046

What is the correct process to pull in a fix?

Bug #55046 has a fix that I would like to pull in. What is the correct way to do this? Barry

Re: Inkscape @0.92.0_3+x11 does not work under macOS Sierra 10.12.3!

I will debug this if someone can tell me how to install the port with source line debug enabled. Also how do I get to see the exact CFLAGS etc that is used in the build? I found that if I build Inkscape outside of MacPorts port file but against MacPorts libs and headers Inkscape works. Barry

Re: Prevent MacPorts editing .bash_profile over and over again...

> On 1 Feb 2017, at 14:20, Bachsau wrote: > > Am 01.02.2017 um 07:38 schrieb Ryan Schmidt: >> Sorry. Repeated modifications of the profile when the modifications were >> already there was a bug. It looks like a fix was committed, so hopefully >> 2.4.1 will not have this bug

Re: port diagnose bug

> On 28 Jan 2017, at 18:40, Mark Bestley wrote: > > port diagnose gives me > > Warning: your $PATH environment variable does not currently include, > /opt/local/bin, which is where port is located. Would you like to add > /opt/local/bin to your $PATH variable now? [Y/N]

Re: Prevent MacPorts editing .bash_profile over and over again...

ed the logs of the installed for unexpected messages. Barry > On 30 Jan 2017, at 20:48, Clemens Lang <c...@macports.org> wrote: > > Hi, > > On Mon, Jan 30, 2017 at 05:37:41PM +, Barry Scott wrote: >>> On 30 Jan 2017, at 12:44, Barry Scott <ba...@

Re: Prevent MacPorts editing .bash_profile over and over again...

> On 30 Jan 2017, at 12:44, Barry Scott <ba...@barrys-emacs.org> wrote: > > When I run the postinstall as me it works are intended for my .bash_profile. > When I run via sudo it looks at root’s file and states tit does not support > the > “sh” shell. I susp

Re: Prevent MacPorts editing .bash_profile over and over again...

When I run the postinstall as me it works are intended for my .bash_profile. When I run via sudo it looks at root’s file and states tit does not support the “sh” shell. I suspect that the environment that postinstall is running in is a strange in some way. (I have seen Mac specific oddities when

Re: Inkscape 0.92.0 now available on MacPorts

> On 4 Jan 2017, at 23:32, David Evans wrote: > > Inkscape 0.92.0 is now available via MacPorts both as an X11 build and as a > native Quartz build. > > If you have MacPorts installed you can build the X11 version using > > sudo port install inkscape > > or the Quartz