Re: I'm already using Homebrew for a couple of things, Is it problematic to use Homebrew and MacPorts side by side?

[Dmitri Zaitsev]

That would interest me too but I have the opposite experience --
I left HB in the exact same (broken) state as it ended up with after using
it for years (with increasingly broken experience) and MacPorts just worked
for me, to the point that it installed packages that would break if
installing from their official sources.

Could you illustrate by an example how the HB can affect them?

On Saturday, August 10, 2019, Mark Anderson  wrote:

> It's possible. But I have had nothing but trouble with it, so much so that
> I just went about fixing the macport port.
>
>
> On Fri, Aug 9, 2019 at 6:44 PM Gerben Wierda  wrote:
>
>> See subject.
>>
>> Gerben Wierda
>> Chess and the Art of Enterprise Architecture
>> 
>> Mastering ArchiMate 
>> Architecture for Real Enterprises
>>  at
>> InfoWorld
>> On Slippery Ice  at EAPJ
>>
>>

-- 
Dmitri Zaitsev
School of Mathematics
Trinity College Dublin

WWW:  http://www.maths.tcd.ie/~zaitsev/

Re: I'm already using Homebrew for a couple of things, Is it problematic to use Homebrew and MacPorts side by side?

[Andrew Udvare]

I can see one way: alias port or the Homebrew command to fix PATH to remove 
either because this is the main point of conflict. And you have to make sure 
you don't install other conflicting commands. So something that is installed 
with MacPorts may also need PATH to be fixed.

Sent from my iPhone

> On Aug 9, 2019, at 18:44, Gerben Wierda  wrote:
> 
> See subject.
> 
> Gerben Wierda
> Chess and the Art of Enterprise Architecture
> Mastering ArchiMate
> Architecture for Real Enterprises at InfoWorld
> On Slippery Ice at EAPJ
> 

Re: I'm already using Homebrew for a couple of things, Is it problematic to use Homebrew and MacPorts side by side?

[Mojca Miklavec]

Dear Gerben,

On Sat, 10 Aug 2019 at 00:44, Gerben Wierda wrote:
>
> See subject.

If you must do it, install HomeBrew to a location other than
/usr/local, make sure that you don't have MacPorts in PATH when
building HB packages from source (not sure if that's still a thing,
they are moving to binary-only), and ideally don't have HB in path
when building for MacPorts, even though MacPorts should usually be
immune to that (unless you have HB in /usr/local, in which case you
are "screwed by definition" and should not expect anything to work
correctly; 
https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-package-managers/).

Mojca

PS: on MacPorts TeX Live works at least all the way down to 10.5 PPC
;), while HB fetches the few gigabytes from MacTeX page which strictly
only supports the last three OSes. That's a pretty good approximation
of different approaches both projects are taking.
https://ports.macports.org/port/texlive-bin

Re: I'm already using Homebrew for a couple of things, Is it problematic to use Homebrew and MacPorts side by side?

[Mark Anderson]

It's possible. But I have had nothing but trouble with it, so much so that
I just went about fixing the macport port.


On Fri, Aug 9, 2019 at 6:44 PM Gerben Wierda  wrote:

> See subject.
>
> Gerben Wierda
> Chess and the Art of Enterprise Architecture 
> Mastering ArchiMate 
> Architecture for Real Enterprises
>  at
> InfoWorld
> On Slippery Ice  at EAPJ
>
>

I'm already using Homebrew for a couple of things, Is it problematic to use Homebrew and MacPorts side by side?

[Gerben Wierda]

See subject.

Gerben Wierda
Chess and the Art of Enterprise Architecture 
Mastering ArchiMate 
Architecture for Real Enterprises 
 at InfoWorld
On Slippery Ice  at EAPJ

nm issue with gimp on 10.5

[Riccardo Mottola via macports-users]

Hi,

I am re-building current GIMP on 10.5 (I have a couple of local patches 
to adapt it, last time they gave me a nice working app).


Buld fails for me with:


.0 -lintl -Wl,-framework -Wl,CoreFoundation -lbabl-0.1   -ljpeg
libtool: link: /usr/bin/nm -p  .libs/gimpmodule.o .libs/pygimp-item.o 
.libs/pygimp-display.o .libs/pygimp-drawable.o .libs/pygimp-image.o 
.libs/pygimp-parasite.o .libs/pygimp-pdb.o .libs/pygimp-tile.o 
.libs/pygimp-vectors.o   |  | /opt/local/bin/gsed 's/.* //' | sort | 
uniq > .libs/gimp.exp

../../libtool: eval: line 1734: syntax error near unexpected token `|'
../../libtool: eval: line 1734: `/usr/bin/nm -p .libs/gimpmodule.o 
.libs/pygimp-item.o .libs/pygimp-display.o .libs/pygimp-drawable.o 
.libs/pygimp-image.o .libs/pygimp-parasite.o .libs/pygimp-pdb.o 
.libs/pygimp-tile.o .libs/pygimp-vectors.o   |  | /opt/local/bin/gsed 
's/.* //' | sort | uniq > .libs/gimp.exp'

make[4]: *** [gimp.la] Error 1


I have already seen this issue months ago, perhaps in another port, I 
don't remember where, the nm version used is too old and using the 
MacPorts one should fix it.


How do I accomplish this? = tried setting NM on the command line but it 
doesn't ork.


I guess the portfile needs a hack... and, in case, can it be done for 
everybody in the official portfile?



Riccardo

Austin Mirror

[Al Varnell via macports-users]

Can someone check out the Autin, TX, USA mirror? Received these results two 
days in a row:

> % port -N -v selfupdate
> --->  Updating MacPorts base sources using rsync
> rsync: failed to connect to aus.us.rsync.macports.org: Operation timed out 
> (60)
> rsync error: error in socket IO (code 10) at 
> /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-52.200.1/rsync/clientserver.c(106)
>  [receiver=2.6.9]
> Command failed: /usr/bin/rsync -rtzvl --delete-after 
> rsync://aus.us.rsync.macports.org/macports/release/tarballs/base.tar 
> /opt/local/var/macports/sources/aus.us.rsync.macports.org/macports/release/tarballs
> Exit code: 10

Ping works:

> % ping aus.us.rsync.macports.org
> PING marmot.tn.utexas.edu (146.6.15.16): 56 data bytes
> 64 bytes from 146.6.15.16: icmp_seq=0 ttl=46 time=63.389 ms
> 64 bytes from 146.6.15.16: icmp_seq=1 ttl=46 time=63.028 ms
> 64 bytes from 146.6.15.16: icmp_seq=2 ttl=46 time=62.394 ms
> 64 bytes from 146.6.15.16: icmp_seq=3 ttl=46 time=63.816 ms
> 64 bytes from 146.6.15.16: icmp_seq=4 ttl=46 time=62.176 ms
> 64 bytes from 146.6.15.16: icmp_seq=5 ttl=46 time=208.555 ms
> 64 bytes from 146.6.15.16: icmp_seq=6 ttl=46 time=62.106 ms
> 64 bytes from 146.6.15.16: icmp_seq=7 ttl=46 time=62.012 ms

-Al-

smime.p7s
Description: S/MIME cryptographic signature