older lib for port

Is it feasible to maintain an older lib to compile a certain port? I wanted to update ngrep 1.45 (sourceforge) to 1.46 (github) and tried compiling in a system that had an older version of libpcap, 1.7.4 (current is 1.8.1). It worked only without the patches. It's far from ideal, but it has no

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

I want to be able to stop MacPorts Installation from editing my .bash_profile. As it happens I already set all the env var that are needed my self. Is there a “do-not-edit-bash-profile” settings somewhere? So far I have 3 sets of the settings in the same file. Barry

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

Hi, It would be better yet if whatever it is that does this first checks to see in the path it is about to add is already in the users PATH, and does not add it again if already there… Chris > On 28 Jan 2017, at 4:31 pm, Barry Scott wrote: > > I want to be able to stop MacPorts Installation

MacPorts 2.4.0 improvements

It is great to see the improvements in MacPorts 2.4.0. Thanks to all the developers! I especially like the new function to print out the notes from ports installed at the end of a big installation or upgrade, e.g., ---> Some of the ports you installed have notes: py27-matplotlib has the follo

Re: Inkscape 0.92.0 now available on MacPorts

> On 27 Jan 2017, at 17:07, Brandon Allbery wrote: > > > On Fri, Jan 27, 2017 at 6:33 AM, Barry Scott > wrote: > Error: Failed to archivefetch gtkmm: gtk2 must be installed with +quartz. > Error: See > /opt/local/var/macports/logs/_opt_local_var_macports_sources

Re: MacPorts 2.4.0 has been released

> On Jan 27, 2017, at 5:06 PM, Clemens Lang wrote: > > Hi, > > On Fri, Jan 27, 2017 at 04:28:46PM -0500, Adam Dershowitz wrote: >> Got it. I was not comfortable running it, without knowing that. Now, >> I see that it is not at irreversible, without asking first. > > That sounds like somet

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

> On 28 Jan 2017, at 16:37, Christopher Jones wrote: > > Hi, > > It would be better yet if whatever it is that does this first checks to see > in the path it is about to add is already in the users PATH, and does not add > it again if already there… That would be an improvement. I would als

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

I think only the pkg installers do that - and they're supposed to not edit the $PATH if $prefix is already in there. (ie if you upgrade using `port selfupdate` I don't think you have that problem). Or am I mistaken? > On Jan 28, 2017, at 4:56 PM, Barry wrote: >> On 28 Jan 2017, at 16:37, Chris