Re: Handing over maintainership

[Mark Anderson]

I know it's been a while, but I just pushed a change for asco and I'm
working on qucs or possibly qucs-s which appears to be actually maintained.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark>
GitHub Profile <https://github.com/markemer>



On Mon, Nov 6, 2023 at 10:24 AM Rolf Wuerdemann  wrote:

> Hi Mark,
>
> On 06.11.23 13:08, Mark Anderson wrote:
> > I'd be interested in qucs and asco as I'm an EE with EDA experience -
> what
> > state are they in?
>
> Thats great news! - To my knowledge, they are working and qucs is up the
> last working version, which ist several years old. Maybe it would be
> better to switch to qucs-s (https://ra3xdh.github.io/) instead ;).
> I can check the current state with my intel mac (10.14?) if needed.
> >
> > —Mark
>
> Kind regards,
>
> Rolf
> > ___
> > Mark E. Anderson mailto:e...@emer.net>>
> > Find me on LinkedIn <https://www.linkedin.com/in/markemer/>
> >
> >
> > On Wed, Nov 1, 2023 at 1:35 PM Rolf Wuerdemann  > <mailto:ro...@digitalis.org>> wrote:
> >
> > Dear colleagues,
> >
> > I've used my mac on a daily level up to around 2009, afterwards,
> > the only usage was (badly provided) maintainership of some ports.
> > Time to make a cut and hand maintainership of "my" ports to
> > someone else but also to recommend discarding some of them:
> >
> > The ports I'd like to hand over are:
> >
> > net/psi
> > science/gwyddion
> > science/qucs
> > science/asco
> >
> > where I've asked for maintainership of gwyddion within their
> community.
> >
> > python/py-pyphant
> > python/py-sogl
> >
> > were ports of my former university group, which was dismissed in
> 2017,
> > therefore I'll recommend to discard these ports.
> >
> > If you like to take maintainership, please give me a sign.
> >
> > Kind regards,
> >
> > rowue
> > --
> > Security is an illusion - data security twice
> > Rolf Würdemann   - ro...@digitalis.org <mailto:ro...@digitalis.org>
> >   -   DL9ROW
> > GnuPG fingerprint:  1B06 8966 A80E 098F B009  999C 1DF7 8938 B57E
> 7BFE
> > xmpp: ro...@digitalis.org <mailto:ro...@digitalis.org> E1189573
> > 6B4A150C A0C2BF5A 5553F865 0B9CBF7A
> > ro...@jabber.ccc.de <mailto:ro...@jabber.ccc.de> 64CBBB68 0A3514A4
> > 026FC1E7 5328CE87 AEE2185F
> >
>
> --
> Security is an illusion - data security twice
> Rolf Würdemann   -   ro...@digitalis.org   -   DL9ROW
> GnuPG fingerprint:  1B06 8966 A80E 098F B009  999C 1DF7 8938 B57E 7BFE
> xmpp: ro...@digitalis.org E1189573 6B4A150C A0C2BF5A 5553F865 0B9CBF7A
>ro...@jabber.ccc.de 64CBBB68 0A3514A4 026FC1E7 5328CE87 AEE2185F
>

Re: Apple Silicon Hardware and MacPorts

[Mark Anderson]

Hell, sometimes, the fans don't even turn on for my short compiles. The
performance per watt of these machines is legendary.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark>
GitHub Profile <https://github.com/markemer>



On Wed, Nov 15, 2023 at 11:26 AM Mark Anderson  wrote:

> I have a M1Max with 64, but I did have an M1 with 16 and most things ran
> faster than on my 2019 Intel Mac. The bump to M3Max might be worth it if
> you do a lot of number crunching or anything that can use a GPU, but even
> the lowest end machines are crazy fast.
>
> The only thing I'll say is that 8GB is not enough on the M3 - don't get
> that one, but 24 should have you zooming along nicely.
>
> —Mark
> ___
> Mark E. Anderson 
> MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark>
> GitHub Profile <https://github.com/markemer>
>
>
>
> On Wed, Nov 15, 2023 at 12:22 AM Daniel J. Luke 
> wrote:
>
>> On Nov 14, 2023, at 10:04 PM, Alexander Newman via macports-users <
>> macports-users@lists.macports.org> wrote:
>> > Are large-ish MacPorts ports going to compile all right on a 24 MB RAM
>> iMac with, say, a 2TB SSD, without the hardware throttling? The same with
>> running R. Do many people on this list use AS machines, and what are their
>> experiences and advice regarding MacPorts on them? Am I in fact
>> over-thinking it?
>>
>> I'll let others chime in for the specific ports you mentioned (as I don't
>> use them) - but for reference I have an M1Pro/16G MacBook Pro and macports
>> + all the ports I care about work fine on it (and it's quite a bit more
>> responsive than my 2018 mac mini).
>>
>> --
>> Daniel J. Luke
>>
>>

Re: Apple Silicon Hardware and MacPorts

[Mark Anderson]

I have a M1Max with 64, but I did have an M1 with 16 and most things ran
faster than on my 2019 Intel Mac. The bump to M3Max might be worth it if
you do a lot of number crunching or anything that can use a GPU, but even
the lowest end machines are crazy fast.

The only thing I'll say is that 8GB is not enough on the M3 - don't get
that one, but 24 should have you zooming along nicely.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage 
GitHub Profile 



On Wed, Nov 15, 2023 at 12:22 AM Daniel J. Luke  wrote:

> On Nov 14, 2023, at 10:04 PM, Alexander Newman via macports-users <
> macports-users@lists.macports.org> wrote:
> > Are large-ish MacPorts ports going to compile all right on a 24 MB RAM
> iMac with, say, a 2TB SSD, without the hardware throttling? The same with
> running R. Do many people on this list use AS machines, and what are their
> experiences and advice regarding MacPorts on them? Am I in fact
> over-thinking it?
>
> I'll let others chime in for the specific ports you mentioned (as I don't
> use them) - but for reference I have an M1Pro/16G MacBook Pro and macports
> + all the ports I care about work fine on it (and it's quite a bit more
> responsive than my 2018 mac mini).
>
> --
> Daniel J. Luke
>
>

Re: Is there anyone who has successfully migrated Macport to Sonoma?

[Mark Anderson]

Xcode 14 will refuse to run on Sonoma - it can run if you trick it, but
that is not a great way to get working software.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage 
GitHub Profile 



On Sun, Oct 8, 2023 at 8:11 PM Joshua Root  wrote:

> On 9/10/2023 10:34, Tao Zhang wrote:
> > Hi Josh,
> >
> >   Thanks for your helpful comments. One more question:
> >
> > gfortran and ifort  do not work after upgrading to Sonoma. see below.
> >   1) Should I upgrade to the latest Xcode15 or old Xcode14 to fix this
> > problem?
> >   2)  It is reported that Xcode15 does not work well with Macport, right?
>
> Yes, there are unfortunately some build issues that affect Xcode 15 but
> not 14. However, as far as I'm aware, Xcode 14 doesn't work on Sonoma.
> So if you need to keep using Xcode 14, you probably also need to stay on
> Ventura.
>
> - Josh
>

Re: Handing over maintainership

[Mark Anderson]

I'd be interested in qucs and asco as I'm an EE with EDA experience - what
state are they in?

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark>
GitHub Profile <https://github.com/markemer>



On Mon, Nov 6, 2023 at 7:08 AM Mark Anderson  wrote:

> I'd be interested in qucs and asco as I'm an EE with EDA experience - what
> state are they in?
>
> —Mark
> ___
> Mark E. Anderson 
> Find me on LinkedIn <https://www.linkedin.com/in/markemer/>
>
>
> On Wed, Nov 1, 2023 at 1:35 PM Rolf Wuerdemann 
> wrote:
>
>> Dear colleagues,
>>
>> I've used my mac on a daily level up to around 2009, afterwards,
>> the only usage was (badly provided) maintainership of some ports.
>> Time to make a cut and hand maintainership of "my" ports to
>> someone else but also to recommend discarding some of them:
>>
>> The ports I'd like to hand over are:
>>
>> net/psi
>> science/gwyddion
>> science/qucs
>> science/asco
>>
>> where I've asked for maintainership of gwyddion within their community.
>>
>> python/py-pyphant
>> python/py-sogl
>>
>> were ports of my former university group, which was dismissed in 2017,
>> therefore I'll recommend to discard these ports.
>>
>> If you like to take maintainership, please give me a sign.
>>
>> Kind regards,
>>
>>rowue
>> --
>> Security is an illusion - data security twice
>> Rolf Würdemann   -   ro...@digitalis.org   -   DL9ROW
>> GnuPG fingerprint:  1B06 8966 A80E 098F B009  999C 1DF7 8938 B57E 7BFE
>> xmpp: ro...@digitalis.org E1189573 6B4A150C A0C2BF5A 5553F865 0B9CBF7A
>>ro...@jabber.ccc.de 64CBBB68 0A3514A4 026FC1E7 5328CE87 AEE2185F
>>
>

Re: ruby

[Mark Anderson]

Yeah, this is the answer. You always want `/opt/local/bin/` to be near the
start of your path. Only stuff that you specifically want to override
MacPorts should be before it. (Examples of things you may want before: RVM
or NVM or any of the version managers that put things in your home)

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage 
GitHub Profile 



On Sat, Mar 11, 2023 at 5:57 PM Austin Ziegler  wrote:

> Change that to
>
> export
> PATH=$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin:$PATH
>
> -a
>
> On Mar 11, 2023, at 14:03, chilli.names...@gmail.com wrote:
>
> 
> Thank you, I will check that
>
> I have
>
> export
> PATH=$PATH:$HOME/bin:/opt/local/bin:/opt/local/sbin:/opt/local/share/man:/usr/X11/bin
>
>
> in my .bash_profile, but echo $PATH shows what you expected:
>
> dude@mac:~$ echo $PATH
>
> /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/dude/bin:/opt/local/bin:/opt/local/sbin...
>
>
> ok, I have something new to work out.
>
> On Mar 11, 2023, at 13:49, Austin Ziegler  wrote:
>
> 
> No problem. The system ruby showing up instead of MacPorts-installed Ruby
> would be *probably* because your $PATH has `/opt/local/bin` *after*
> `/usr/bin`. Typically, one wants to have Macports (or other third-party
> package systems) *before* /usr/local/bin and /usr/bin.
>
> -a
>
> On Sat, Mar 11, 2023 at 1:46 PM chilli.names...@gmail.com <
> chilli.names...@gmail.com> wrote:
>
>> 
>>
>> root@mac:~$ ruby -S gem install coltrane
>> ERROR:  Error installing coltrane:
>> activesupport requires Ruby version >= 2.7.0.
>>
>>
>> Unfortunately, Mojave:
>> ruby 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin18]
>>
>> So I install ruby 2.7.7
>>
>> root@mac:~$ port -vsN install ruby27
>>
>> 
>> --->  Cleaning ruby27
>> --->  Removing work directory for ruby27
>> --->  Updating database of binaries
>> --->  Scanning binaries for linking errors
>> --->  No broken files found.
>> --->  No broken ports found.
>> --->  Some of the ports you installed have notes:
>> ruby27 has the following notes:
>> To make this the default Ruby (i.e., the version run by the 'ruby', 'gem'
>> or 'bundle' commands), run:
>> sudo port select --set ruby ruby27
>> root@mac:~$ port select --set ruby ruby27
>> Selecting 'ruby27' for 'ruby' succeeded. 'ruby27' is now active.
>> root@mac:~$ ruby -S gem install coltrane
>> ERROR:  Error installing coltrane:
>> activesupport requires Ruby version >= 2.7.0.
>>
>>
>> grrr... it's still trying to use /usr/bin/ruby
>>
>> but
>>
>> root@mac:~$ /opt/local/bin/ruby -S gem install coltrane
>>
>>
>> installed it.
>>
>> idky my ruby $PATH seems stuck on /usr/bin/ruby, but thanks to your tip,
>> I was able to  install coltrane, and it seems to be working. Neato CLI
>> music utility.
>>
>> Thank you, Austin!
>>
>> On Mar 11, 2023, at 13:14, Austin Ziegler  wrote:
>>
>> 
>> I don’t use Macports Ruby (I use `ruby-install`), but try this:
>>
>> sudo ruby -S gem install coltrane
>>
>> Ruby since Ruby 2.x has included Rubygems, and since a bit later than
>> that, Bundler.
>>
>> -a
>>
>> On Sat, Mar 11, 2023 at 1:06 PM chilli.names...@gmail.com <
>> chilli.names...@gmail.com> wrote:
>>
>>> Hi,
>>> I need a quick ruby primer, please.
>>>
>>> I'd like to install this,
>>> https://github.com/pedrozath/coltrane
>>>
>>> sudo gem install coltrane
>>>
>>>
>>> won't work because I'm on Mojave with an an ancient ruby and this
>>> requires ruby 2.7 or above.
>>>
>>> sudo port -vsN install ruby
>>>
>>>
>>> installs ruby18 by default
>>>
>>> sudo port -vsN install ruby27
>>> sudo port select --set ruby ruby27
>>>
>>>
>>> installs, but gem still complains.
>>>
>>> just guessing at this point:
>>>
>>> port -vsN install rb-rubygems
>>>
>>>
>>> reinstalls ruby18 ><
>>>
>>>
>>> Help, please.
>>>
>>
>>
>> --
>> Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
>> http://www.halostatue.ca/ • http://twitter.com/halostatue
>>
>>
>
> --
> Austin Ziegler • halosta...@gmail.com • aus...@halostatue.ca
> http://www.halostatue.ca/ • http://twitter.com/halostatue
>
>

Re: Sandbox issues with Swift Package Manager

[Mark Anderson]

Ah ok , that's above my paygrade right now - I had no idea we were doing
that. I've copied the dev list - I think the response will be better over
there.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark>
GitHub Profile <https://github.com/markemer>



On Fri, Dec 10, 2021 at 5:12 PM Andrew Udvare  wrote:

>
> > On 2021-12-10, at 13:01, Mark Anderson  wrote:
> >
> > SPM and Workspace builds need to be added to the XCode portgroup - it's
> something that I've been working on for a while.
> >
> > I'm a little surprised the sandbox is involved at all. Is it XCode's
> sandbox complaining? Or is it Terminal? Make sure the terminal has full
> disk access.
>
> This is sandbox-exec(1) complaining. When I run the same xcodebuild
> command without MacPorts the build works fine in the same terminal.
>
>
> https://github.com/macports/macports-base/blob/master/src/port1.0/portsandbox.tcl

Re: Sandbox issues with Swift Package Manager

[Mark Anderson]

SPM and Workspace builds need to be added to the XCode portgroup - it's
something that I've been working on for a while.

I'm a little surprised the sandbox is involved at all. Is it XCode's
sandbox complaining? Or is it Terminal? Make sure the terminal has full
disk access.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage 
GitHub Profile 



On Fri, Dec 10, 2021 at 7:57 AM Andrew Udvare  wrote:

> I am testing out how to build Xcode-based packages that use Swift
> Package Manager (SPM) and it seems even with 'hacks' to make Xcode not
> do any downloading of code, there's still some network activity (or
> something the sandbox is blocking) that I have not figured out.
>
> Example port: https://github.com/Tatsh/ports/tree/master/aqua/eul
>
> Try using this with `port -d destroot` to see everything. You will get
> this error:
>
> Resolve Package Graph
>
> sandbox-exec: sandbox_apply: Operation not permitted
>
> sandbox-exec: sandbox_apply: Operation not permitted
>
> sandbox-exec: sandbox_apply: Operation not permitted
>
> sandbox-exec: sandbox_apply: Operation not permitted
>
> cannot update Package.resolved file because automatic resolution is
> disabledxcodebuild: error: Could not resolve package dependencies:
>sandbox-exec: sandbox_apply: Operation not permitted
>sandbox-exec: sandbox_apply: Operation not permitted
>sandbox-exec: sandbox_apply: Operation not permitted
>sandbox-exec: sandbox_apply: Operation not permitted
>cannot update Package.resolved file because automatic resolution is
> disabled
>fatalError
>
> Thoughts on how this can be worked around? If anyone figures out what
> these blocked operations were I'd be very interested in knowing.
>
> Thanks
> Andrew
>

Re: is macports getting rusty?

[Mark Anderson]

I think this is more a reflection of the open source landscape than
anything we're doing.

py-cryptography, for example, is 8% Rust, according to Github. I don't know
when they added it, but the latest version needs it. Same goes for rav1e.
It's one-third Rust.

Along with Go, you're going to see more and more Rust. I think the only way
around that is waiting for a binary package.

—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage 
GitHub Profile 



On Sun, Nov 28, 2021 at 11:37 PM Kastus Shchuka  wrote:

> Dear macports users,
>
> Recently, more and more ports began to depend on rust and cargo.
>
> Maybe rust is a wonderful language that will solve all problems of the
> world. I just wonder, if it is so good, why it takes forever and a day
> (literally)  to compile? I've never seen anything taking that long to
> build.
>
> I've been using graphviz port for over 10 years, I guess. I had to delete
> it today.
>
> graphviz depends on gd2. gd2 depends on libheif. libheif depends on rav1e.
> Now rav1e started depending on cargo-c, nasm, clang-13, cargo.
> An attempt to upgrade rav1e launched a build of cargo-c which I had to
> kill as I did not have luxary to wait for tens of hours for it to finish.
>
> I either have to keep outdated ports or stop using them and delete.
> Unfortunately, the usable surface of macports started shrinking for me (or
> should I call it "rusting"?).
>
> Another example is py-cryptography, which now requires rust to build.
> Until binary package was made available, it took me over a day to upgrade
> py-cryptography.
>
> I also now have a broken ImageMagic because its dependency chain pulls in
> rust. And the list goes on and on.
>
> I doubt people who rushed rust into macports are going to reconsider their
> decisions. I am just sharing my experience with this "rusting"
>
> Thank you for reading.
>
> -Kastus

Re: New ports.macports.org website

[Mark Anderson]

I love it - great work.


—Mark
___
Mark E. Anderson 
MacPorts Trac WikiPage 
GitHub Profile 



On Mon, Jul 19, 2021 at 4:08 PM Mojca Miklavec  wrote:

> Dear MacPorts users and developers,
>
> I'm really thrilled to see the new version of the ports website
> finally being deployed at
>  https://ports.macports.org
>
> I'm extremely grateful for the excellent work that Arjun did during
> the GSOC summers of 2019 and 2020. He kept maintaining the code after
> GSOC and made the migration to his own server (the previous server was
> running out of resources to be able to cope with the additional
> requirements introduced in the last summer).
>
> Many thanks also to Amar with a much deeper understanding of Django
> and related technologies who co-mentored the project in 2020 and made
> sure that we ended up with a product of much higher quality than any
> one of us could have achieved.
>
> Some exciting new features involve:
> - Dark mode.
> - Better REST API.
> - Remove dependency on Google Charts (blocked in some parts of the world).
> - More advanced / extensive search & filtering for ports.
> - Find ports that provide a particular file.
> - The site runs livecheck and reports outdated ports.
> - Ability to log in with GitHub OAuth and follow your favourite ports.
> You can check whether they are outdated or broken on some platforms,
> making it easier to see where contributions are needed.
>
> You can read a bit more about the project on Arjun's blog:
> https://arjunsalyan.com/gsoc20-report/
>
> The code lives at
> https://github.com/macports/macports-webapp
>
> We would be most happy to see contributions to this project, both in
> terms of programming as well as for design, ideas etc.
> Arjun did an impressive job already (everything from backend to
> design), but if we have some talented designers around, please speak
> up.
>
> I would also like to invite everyone who hasn't done that already to
> opt-in for anonymous statistics submissions:
>
> sudo port install mpstats
>
> Thank you,
> Mojca
>
> PS: The old version will still live at
> https://port-old.macports.org
> for a little while, just in case.
>

Re: OpenMPI Users - Is Anyone Using openmpi-clang33 or openmpi-clang34?

[Mark Anderson]

Yeah. I don’t know I ever use MPI in anything less than the latest clang or
maybe one version back if they broke something.

—Mark

On Fri, May 7, 2021 at 3:11 PM Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

> Yes, gcc7 works down to 10.4, both PPC and Intel and is the primary
> compiler there.  I can see no need for openMPI to support any older gcc.
>
> clang-3.3, clang-3.4, and clang-3.7 should not be used for anything other
> than bootstrapping to newer clangs now.
>
>
> Ken
>
>
> --
Sent from Gmail Mobile on iPhone

Re: MacPorts and Anaconda

[Mark Anderson]

Yeah, I've found pyenv works for this as well, and rvm also works for ruby.

—Mark

On Mon, Aug 12, 2019 at 3:22 AM Ruben Di Battista 
wrote:

> This can be applied also to virtualenv. What you need to do, imho, is to
> just create conda envs. They're isolated from system interpreters and they
> should not collide with anything. In these envs you can install whatever
> you want... And keep it from interfering with system packages...
>
>
>
> On Mon, 12 Aug 2019, 07:55 Fielding, Eric J (US 329A) via macports-users, <
> macports-users@lists.macports.org> wrote:
>
>> I saw the discussion the last few days about the problems with using both
>> HomeBrew and MacPorts on the same system. I was wondering about problems
>> with using MacPorts and Anaconda to install different packages. I have been
>> using MacPorts for a long time with few problems, but sometimes I need
>> newer versions of Python packages or I need to install something that is
>> available as a conda package. It seems that Anaconda is specifically
>> designed to keep separate copies of the things it needs and switch between
>> environments, so I assume that there should be fewer problems with MacPorts
>> than using something like HomeBrew.
>>
>>
>>
>> Thanks,
>>
>> ++Eric
>>
>> Pasadena, California
>>
>

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
>
>

Re: Catalina

[Mark Anderson]

I can open feedback via radar or whatever as I’m in the developer program
 but also they loosened the NDA a bit a few years back. A bunch of us made
a fuss sometime after swift came out since it was vital to help each other
before the release. That’s why you can learn about SwiftUI and the like on
the Internet today even with the NDA in place. That said, look up the
restrictions. Things like screenshots are forbidden. And we should probably
just discuss among those of us with a developer account (or public beta)
but I don’t know that agreement.

—Mark

On Mon, Jul 8, 2019 at 8:25 PM Al Varnell via macports-users <
macports-users@lists.macports.org> wrote:

> I would not be allowed to even say if I was, but my understanding is that
> Feedback submissions from the public beta program are only considered in
> aggregate and never responded back to individuals.
>
> Sent from my iPad
>
> -Al-
>
> > On Jul 8, 2019, at 12:53, Peter Homann  wrote:
> >
> > NDA.
>
> --
Sent from Gmail Mobile on iPhone

Re: Catalina

[Mark Anderson]

I am.

On Mon, Jul 8, 2019 at 3:53 PM Peter Homann  wrote:

> Anyone else on the MacOS beta program and now have Catalina? I have an
> issue I want to discuss, but without breaching the NDA.
>
> I have logged my issue through Apple's feedback process, but I would guess
> their first response will be that it isn't a MacOS problem, but a Macport
> issue.
> Thanks in advance,
> Peter
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Sent from Gmail Mobile on iPhone

Re: TeXLive distribution and macports

[Mark Anderson]

Yeah, this is specifically prohibited by our guidelines and the overall
workings of the program. There is a TeXlive minimum install, and if you
could make one smaller that works with lily pond I’m sure we’d consider it.
But this is basically a non-starter with MacPorts.

—Mark

On Sun, Sep 9, 2018 at 12:31 PM Werner LEMBERG  wrote:

>
> >> Ah, I assumed too much knowledge, sorry.  TeXLive itself comes with
> >> binaries for MacOS (both legacy platforms, i.e., 10.6-10.10, and
> >> recent versions, i.e., 10.10-10.13).  By simply prepending the path
> >> to those binaries to PATH, the `texlive-*' ports from MacPorts
> >> would be completely hidden and thus useless, more or less: TeXLive
> >> wouldn't use any data, binaries, or libraries from MacPorts.
> >>
> >> However, to build various packages like `lilypond', `port' needs to
> >> believe that some `texlive-*' ports are installed.  What certainly
> >> works is to create a small port repository similar to René Bertin's
> >> `macstrop' repository to override MacPorts with dummy ports.  My
> >> question was whether macports itself provides a simpler solution
> >> similar to `texlive-dummy-opensuse', where I have to install just a
> >> single .rpm file...  I guess the answer is no.
> >
> > Its quite simple.  The macports build of lilypond should be
> > configured to use the MacPorts provided builds of TexLive.
>
> I was still unclear, sorry.  To continue with lilypond as an example:
> This program uses only TeXLive *programs* and data, but no libraries.
> In general, this is true for all other programs within MacPorts that
> depend on texlive ports.  It is thus irrelevant whether MacPorts
> itself contains the necessary data and binaries, or whether they are
> provided externally (in this case, by the native TeXLive
> distribution).
>
> > If these ports do not provide what is needed, then just provide an
> > additional port for what is missing.
>
> There are no misses.  My `problem' is that the `texlive-*' ports
> within MacPorts use a few GByte, doubling everything native TeXLive
> already provides!  I want to use native TeXLive directly so that I can
> actually call `tlmgr' (or the SVN repository) to update the TeX stuff.
> For this reason I want to have some dummy portfiles to make `port'
> believe that the `texlive-*' ports are present.  This will take a few
> kBytes only...
>
>
> Werner
>
-- 
Sent from Gmail Mobile on iPhone

Re: iTerm2 and High Sierra 10.13.6 incompatible...

[Mark Anderson]

Yeah, open a ticket. I'll take a look. I think we stopped the autoupdate
dialog before, but it moved around on us. I need to bump to at least 3.1.7
anyway.

—Mark
___
Mark E. Anderson 


On Wed, Jul 18, 2018 at 3:43 PM Richard L. Hamilton 
wrote:

>
>
> > On Jul 18, 2018, at 15:20, Ryan Schmidt  wrote:
> >
> >
> >
> > On Jul 18, 2018, at 14:17, Richard L. Hamilton wrote:
> >
> >> But...as soon as I tried to run it, it popped up its own updater
> telling me that 3.1.7 was available.  Now I know enough NOT to use a
> non-MacPorts updater on something installed via MacPorts, but IMO, the
> MacPorts build really should (if there's a way to do it) disable the
> built-in updater, so as not to tempt people to do the wrong thing.
> >
> > Yes; by all means file a ticket about that.
> >
>
> Hmm.  I looked at the source, and there don't appear to be any #ifdefs or
> anything like that to provide a build option to disable auto-update.  So
> the scope of that might be such that it'd be an issue for upstream,
> assuming they're interested, which they might not be, since they also
> distribute binaries themselves.
>
> A note on the port telling people not to use that, and suggesting that
> they un-check "Check for updates automatically" in the General tab of the
> iTerm2 Preferences, might be a minimalist improvement on nothing at all,
> anyway.
>
> What do you suggest?  Would the note be sufficient?  And if not, where
> should the ticket be filed, with MacPorts, or upstream?
>
>

Re: iTerm2 and High Sierra 10.13.6 incompatible...

[Mark Anderson]

Did you open a ticket? What exactly is wrong? What hardware are you
running? Are there any logs?

It runs on 10.13 and 10.14 for me just fine.

—Mark
___
Mark E. Anderson 


On Tue, Jul 17, 2018 at 6:12 PM Eitan Adler  wrote:

> On Tue, 17 Jul 2018 at 15:04, Comer Duncan  wrote:
> >
> > Today I upgraded my os to 10.13.6 and immediately saw that iTerm2 does
> not work at all.
>
> What's the exact problem you're seeing? I'm not seeing any issues with
> 10.3.6 + iTerm2.
>
>
>
> --
> Eitan Adler
>

Re: installation on OS X 10.14 beta

[Mark Anderson]

That's a bad idea. I have to build 100% from source. One of the prices for
using the beta. The upside is most of them work fine.
—Mark
___
Mark E. Anderson 


On Wed, Jul 4, 2018 at 12:06 PM Manav Bhatia  wrote:

> Hi,
>
>  I am wondering if it is possible for MacPorts to install packages from
> prebuilt binaries on 10.14 beta. Is it possible force this? Maybe there is
> a way to tell MacPorts to assume 10.13 even though it is running on 10.14?
>
> Thanks,
> Manav
>
>

Re: High Sierra and MacPorts

[Mark Anderson]

My old MacBook 10,1 with 16GB runs faster, it seems to be following the
speedup of versions 10.6, 10.8, and 10.11

—Mark
___
Mark E. Anderson 

On Sun, Oct 8, 2017 at 9:24 PM, Arno Hautala  wrote:

> I can't speak to slowness on your machine, but I haven't seen a
> noticeable difference on my own (Mid-2013 MacBook 8GB).
> MacPorts is running well and only a handful of ports are having
> issues. I think not everything is available as a binary yet, but
> progress continues.
>
> On Sun, Oct 8, 2017 at 9:04 PM, Dave Horsfall  wrote:
> > Now that MacPorts is on 2.4.2, is High Sierra now fair game?  Is it
> likely
> > to be even more bloated and slower on my old 4GB MacBook than before?
> >
> > Thanks.
> >
> > --
> > Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> > suffer."
>
>
>
> --
> arno  s  hautala/-|   a...@alum.wpi.edu
>
> pgp b2c9d448
>

Re: macports' hardlinks and time machine backups

[Mark Anderson]

Call du with --si and you should get numbers that match.

—Mark
___
Mark E. Anderson 

On Mon, Aug 14, 2017 at 8:16 AM, Rainer Müller  wrote:

> On 08/13/2017 07:57 PM, db wrote:
> > On 13 Aug 2017, at 18:46, Clemens Lang  wrote:
> >> MacPorts no longer uses hardlinks. We now keep the pristine state in
> archives in /opt/local/var/macports/software instead of hardlinking
> everything from there.
> >
> > Not even for other parts that I'm not aware of, that would explain the
> difference between Finder and du?
>
> Finder on macOS uses base 10, so "GB" stands for 1000*1000*1000 Bytes.
> du(1) uses base 2, so "G" means 1024*1024*1024 Bytes.
>
> https://support.apple.com/en-us/HT201402
>
> Rainer
>

Re: Migration Assistant moved MacPorts home directories

[Mark Anderson]

I think the "best" course of action for you is to delete all the users and
then follow the migration instructions. But yeah, there has to be some way
to undo this damage programmatically.

—Mark
___
Mark E. Anderson 

On Wed, Mar 1, 2017 at 6:39 PM, Ryan Schmidt 
wrote:

>
> > On Mar 1, 2017, at 17:07, Bradley Giesbrecht 
> wrote:
> >
> >> On Feb 28, 2017, at 9:54 PM, Ryan Schmidt 
> wrote:
> >>
> >> I've just used Migration Assistant to migrate from one Sierra system to
> another. Since both systems are the same macOS version, I wasn't planning
> on following the Migration instructions in the wiki. (I was planning on
> rebuilding gmp, since I know it builds for a specific processor.) I ran
> into a problem that I haven't heard discussed before and I don't see
> addressed in the Migration instructions.
> >>
> >> The problem is that the Migration Assistant explained that it would
> relocate users' home directories to the /Users directory -- all those users
> accounts that MacPorts had created for the various ports I've installed
> over the years. (cyrus, postgres, rabbitmq, snort, squid, etc.) And also
> MacPorts' own macports user account. It not only moved the home directories
> into /Users, it also added the standard directories (Desktop, Documents,
> Downloads, Library, Movies, Music, Pictures) to each one, and edited the
> user account so that its NFSHomeDirectory attribute points to the new
> location.
> >>
> >> Obviously, I didn't want Migration Assistant to do any of that. But I
> didn't appear to be given much choice. For each user account, there was
> only a checkbox, which I kept checked because I wanted the users
> transferred to the new machine. I did not know what would happen if I
> unchecked the checkboxes: Would those user accounts and their home
> directories not be migrated? Would the user accounts be migrated without
> their home directories? Would the user accounts be migrated with the home
> directories kept in the original locations?
> >>
> >> It looks like MacPorts automatically recreates its home directory in
> the normal location, but does not update the NFSHomeDirectory attribute of
> the user account.
> >>
> >> What should users do if they are in this situation? Manually move each
> home directory back to where it belongs, delete the standard directories,
> and edit the user account's NFSHomeDirectory attribute? (That's a lot of
> work.) Is there anything users can do during or before migration to avoid
> this situation?
> >
> > I have no answer but building a port migration tool sounds like a good
> GSoC 2017 project.
>
> What do you think this tool should do?
>
>

Re: Migration Assistant moved MacPorts home directories

[Mark Anderson]

Yeah, I've never used the migration assistant since it has always caused me
heartache, but I bet we have a lot of users that do. It's an interesting
case. We should at least come up with advice as to how to get rid of all
this crap and start fresh.

—Mark
___
Mark E. Anderson 

On Wed, Mar 1, 2017 at 6:10 PM, Ryan Schmidt 
wrote:

>
> > On Mar 1, 2017, at 17:09, Brandon Allbery  wrote:
> >
> >
> > On Wed, Mar 1, 2017 at 12:54 AM, Ryan Schmidt 
> wrote:
> > I've just used Migration Assistant to migrate from one Sierra system to
> another. Since both systems are the same macOS version, I wasn't planning
> on following the Migration instructions in the wiki. (I was planning on
> rebuilding gmp, since I know it builds for a specific processor.) I ran
> into a problem that I haven't heard discussed before and I don't see
> addressed in the Migration instructions.
> >
> > Frankly, I'd consider this an example of why trying to shortcut around
> the Migration instructions is a bad idea.
>
> The migration instructions are for migrating from one CPU arch to another,
> or from one macOS version to another. Neither applies here.
>
>