On Jun 5, 2022, at 12:42, Jim DeLaHunt wrote:
>
>>> …Thus I succeeded in fumbling my way through installing gimp +quartz
>>> despite dependencies already present with the wrong variants, but it was a
>>> bit messy and confusing. Should I expect MacPorts to do a better job with
>>> this
On Jun 5, 2022, at 15:49, Craig Treleaven wrote:
> In the past, I’ve had to blow away my git clone (not fork) from time to time
> when I messed up something. That’s the reason I’ve kept both the standard
> MacPorts-installed tree and the git clone. Is there any harm in having both?
No
On Jun 7, 2022, at 03:20, Christoph Kukulies wrote:
> I’m not sure whether I can harmlessly use brew to install a package that is
> not available under macports, to be precise, sigrok/pulseview is the target.
>
> All available remedies refer to using brew install.
>
> May I use brew along with
On Jun 3, 2022, at 02:38, Michael Newman wrote:
>
> After: sudo port -u upgrade outdated
>
> Error: Failed to archivefetch py310-markdown: Failed to fetch signature for
> archive: The requested URL returned error: 503
>
> Then:
>
> sudo port install py310-markdown
> ---> Computing
On Jun 1, 2022, at 17:31, Jim DeLaHunt wrote:
> Should I expect a +quartz variant to propagate to dependencies, and overrule
> existing variants?
Variants specified on the command line when installing a port propagate to any
dependencies that have not yet been installed. They do not propagate
Please continue to Reply All so that the conversation stays on the mailing list.
On May 31, 2022, at 18:40, James wrote:
> On 1 Jun 2022, at 7:19 am, Ryan Schmidt wrote:
>
>> I have not used gimp often enough to be familiar with the option you're
>> referring to so I'm not
On Jun 2, 2022, at 20:44, Craig Treleaven wrote:
> I’m a port maintainer…but I’m having a user problem. For some weeks now,
> ‘sudo port selfupdate’ has not been properly updating my local ports tree(s)
> on my main Mac. About 2 weeks ago, I was going to post a question about this
> but then
On May 30, 2022, at 18:47, James wrote:
> The gimp.dmg version behaves as expected. The macports version does not
>
> File->save->Overwrite option is missing
I have not used gimp often enough to be familiar with the option you're
referring to so I'm not sure I can advise you properly. However
On May 21, 2022, at 10:22, Bill Cole wrote:
> I'm currently working on a OSS project (SpamAssassin) which is in a
> pre-release rush and which I ultimately test & deploy via MacPorts.
>
> I'd *like* to be able to switch from the current supported release in
> MacPorts to a fresh build from a
On May 8, 2022, at 10:37, Ryan Schmidt wrote:
>
> On May 8, 2022, at 05:43, Ralph Seichter wrote:
>
>> My attempt to build rebar3 @3.12.0 fell flat today, and I found the Trac
>> ticket https://trac.macports.org/ticket/62962 . There have not been any
>> updates to th
On May 8, 2022, at 05:43, Ralph Seichter wrote:
> My attempt to build rebar3 @3.12.0 fell flat today, and I found the Trac
> ticket https://trac.macports.org/ticket/62962 . There have not been any
> updates to this ticket for a year, and I wonder if the rebar3 port is
> actively maintained?
On May 7, 2022, at 09:43, JEFFRY KILLEN wrote:
> On May 7, 2022, at 1:11 AM, Ryan Schmidt wrote:
>
>> "MAMP" stands for "macOS, Apache, MySQL or MariaDB, and PHP" but I assume
>> you meant you installed those outside of MacPorts. If so, you probably onl
On May 5, 2022, at 11:14 PM, JEFFRY KILLEN wrote:
> I installed php80 and ran php -v in the terminal.
> Command not found was the response.
>
> I looks like there was no command line version of
> php with Monterey as well as no module. But it is not
> clear where the php executable would be
On May 3, 2022, at 11:13, Максим Овчаренко wrote:
> (macports) sudo port -d selfupdate i was do all same action like the
> instruction wrote write an answer how to fix
> https://guide.macports.org/#installing
What problems are you experiencing? The log you attached didn't show any
problems.
On May 2, 2022, at 23:49, Sriranga Veeraraghavan wrote:
> On May 2, 2022, at 20:46, Ryan Schmidt wrote:
>
>> When the MacPorts installer detects that your shell is zsh, it places such a
>> line in ~/.zprofile. I don't know if there is a significant difference
On May 2, 2022, at 14:04, Sriranga Veeraraghavan wrote:
> Regarding nvim, the reason that zsh can’t find it is probably that the
> directory /opt/local/bin is not included zsh's PATH environment variable.
Right. The MacPorts installer sets up the PATH for your current shell. If you
change
On Apr 30, 2022, at 02:08, Mike Alexander wrote:
> However there is at least one thing Apple installed that depends on Python.
> The Automator action "Combine PDF Pages" fails because it tries to use the
> copy of Python that has been removed.
I trust you have reported this problem to Apple.
On Apr 30, 2022, at 22:32, Christian Calderon wrote:
>
> I'm trying to install curl on my PowerMac G5 running Mac OS X Tiger, but I
> can't because of this circular dependency. Any advice?
I inadvertently introduced a circular dependency and need to resolve it.
On Apr 21, 2022, at 17:08, Lars Sonchocky-Helldorf wrote:
> I have a general question: What to do with outdated ports? File a bug at
> GitHub?
>
> Specifically, we are talking about this port: QEMU. Here is a new version:
> https://wiki.qemu.org/ChangeLog/7.0 which I would like to see in
On Apr 17, 2022, at 20:15, Dave Horsfall wrote:
> [ Late reply; sorry ]
>
> On Sun, 13 Mar 2022, Ryan Schmidt wrote:
>
>>> I'm quite taken by the progress bar on "cmake"; it keeps changing its
>>> mind, just like a MacOS upgrade does :-)
>>
&g
On Apr 17, 2022, at 09:45, Christian Calderon wrote:
>> You would not be able to make a symbolic link at /usr/bin/python because
>> /usr/bin is a protected directory.
>
> TIL. Is that something I could work around by disabling SIP?
On macOS 10.x, yes. On macOS 11 and later, my understanding
On Apr 17, 2022, at 09:13, Christian Calderon wrote:
> I’m on 12.3 on all my macs, and I haven’t noticed anything broken in MacPorts
> because of the removal of python. If I ram into something that needed
> /usr/bin/python I’d just make a symbolic link to MacPorts python 2.
You would not be
On Apr 17, 2022, at 08:49, Gerben Wierda wrote:
> The question I have when moving from 12.2 to 12.3 is: is there a port in my
> set that depends on /usr/bin/python (and should become dependent on a
> MacPorts python instead)?
There are innumerable ways that python might be referenced in a
On Apr 16, 2022, at 08:43, Ralph Seichter wrote:
>
> It is also worth mentioning that I use this machine for a lot of Python
> software development. Works just fine.
The python ports and the python module ports are not the ones that are affected
by the problem. The ones affected by the problem
On Apr 16, 2022, at 08:16, Gerben Wierda wrote:
> I’m about to take the plunge and move one of my systems to macOS 12.3 (which
> removes /usr/bin/python). I am going to consider that a MacPorts major
> migration (so following the migration instructions).
If you are upgrading from macOS 11.x or
On Apr 16, 2022, at 16:46, Sriranga Veeraraghavan wrote:
> I’m running MacPorts 2.7.2 on Big Sur 11.6.5 with Xcode 12.5.1. I have put
> off upgrading to Xcode 13 so far, but I would like to upgrade soon because I
> understand that there are some security fixes in the latest Xcode 13.x that
>
On Apr 14, 2022, at 04:57, Richard L. Hamilton wrote:
> Would use of @loader_path as in @loader_path/../lib or whatever when linking
> binaries (and something similar for linking between libraries within
> MacPorts) not be a big part of making it so the executables and libraries
> didn't
On Apr 14, 2022, at 14:34, Daniel J. Luke wrote:
> On Apr 14, 2022, at 2:56 PM, Peter Serocka wrote:
>
>> Error: Current platform "darwin 19" does not match expected platform "darwin
>> 18"
>> Error: If you upgraded your OS, please follow the migration instructions:
>>
> On Apr 14, 2022, at 15:24, chilli.names...@gmail.com wrote:
>
>> Error: Current platform "darwin 19" does not match expected platform "darwin
>> 18"
>> Error: If you upgraded your OS, please follow the migration instructions:
>> https://trac.macports.org/wiki/Migration
>> OS platform
On Apr 14, 2022, at 04:34, Peter Serocka wrote:
> Sure. On the other hand -- let me suggest MacPorts to adopt
> OS/architecture-specific prefixes by default. Transitions will benefit, in
> particular in cases where "some" ports are troublesome.
I don't think there's any chance of that
On Apr 13, 2022, at 03:32, Peter Serocka wrote:
> FWIW, I have found it useful to install MacPorts under a new prefix
> with every MacOS/Darwin release (like /opt/macports##).
By doing that you'll miss out on being able to receive precompiled binaries
from us and will have to compile
On Apr 11, 2022, at 17:02, Dave Horsfall wrote:
> On Mon, 11 Apr 2022, Ryan Schmidt wrote:
>
>> Run "sudo port selfupdate" to get the most recent ports.tar. Do you
>> still see the problem then?
>
> I did run that first; apologies for not mentioning it (ther
On Apr 11, 2022, at 21:10, Jim DeLaHunt wrote:
> Might the presence of "archs='x86_64'" cause the restore_ports.tcl script to
> ask for +universal variants on the new computer?
>
> Should I perhaps null out the value "x86_64" from the archs entries in my
> installed ports list? i.e. turn
On Apr 10, 2022, at 16:31, Dave Horsfall wrote:
> Early MacBook Pro, High Sierra 10.13.6, MacPorts 2.7.2.
>
> When doing my weekly MacPorts maintenance (doesn't everyone?), I saw this
> during a "port reclaim" (automatically requested):
>
>Found no inactive ports.
>---> Building list
On Apr 9, 2022, at 14:33, Werner LEMBERG wrote:
>>> ```
>>> ccache /opt/local/bin/clang-mp-13 ... conftest.c >&5
>>> ccache: error: Failed to create temporary file for
>>> /run/user/507/ccache-tmp/tmp.cpp_stdout.RTVNqj: Operation not permitted
>>> ```
>>>
>>> What's the reason that `port` tries
On Apr 7, 2022, at 10:56, Mark Lucas wrote:
> The current MacPorts version of get_iplayer 3.27 is out of date. Recent
> updates appear to include a number of significant changes, the current
> version stands at 3.29
> Any chance of an update to the MacPorts package to the latest version?
Port
On Apr 8, 2022, at 17:40, James Secan wrote:
> I’m just getting started on php, and started by putting php81 on a Big Sur
> system. While looking at how to tweak the configuration on this setup, I
> find that I need libphp8.0.so. The Apple setup for apache2 has libphp7.so,
> but nothing for
On Apr 5, 2022, at 13:04, Stanton Sanderson wrote:
> Wondering if anyone else has found problems with the latest update of
> Lilypond-devel (to v 2.23.7) on Big Sur (11.6.5) and Frescobaldi (3.1.3)… Had
> to revert to Lilypond-devel 2.23.6.
Would you care to specify what those problems were?
On Apr 5, 2022, at 09:08, Christoph Kukulies wrote:
> Thanks. Assumed I have downloaded a binary release from libusb’s github
> Releases and it looks like that in the tree:
>
> $ find macos_11.6
> macos_11.6
> macos_11.6/.DS_Store
> macos_11.6/bin
> macos_11.6/bin/dpfp
> macos_11.6/bin/listdevs
On Apr 4, 2022, at 14:25, Dave Allured - NOAA Affiliate wrote:
>
> On Sun, Apr 3, 2022 at 4:23 PM Ryan Schmidt wrote:
>> On Apr 1, 2022, at 13:09, Artemio González López wrote:
>>
>> > After executing “port diagnose” in my 2020 13” MacBook Pro running the
>>
On Apr 1, 2022, at 13:09, Artemio González López wrote:
> After executing “port diagnose” in my 2020 13” MacBook Pro running the latest
> version of the operating system (Monterrey 12.1.3, I believe) I got the
> following output:
>
> Warning: objc[10836]: Class
On Apr 1, 2022, at 13:38, Werner LEMBERG wrote:
>
> ```
> ccache /opt/local/bin/clang-mp-13 ... conftest.c >&5
> ccache: error: Failed to create temporary file for
> /run/user/507/ccache-tmp/tmp.cpp_stdout.RTVNqj: Operation not permitted
> ```
> What's the reason that `port` tries to use
On Apr 1, 2022, at 22:26, Peter West wrote:
> I’m following dependencies which have their own dependency on qt4-mac and are
> set to universal, I presume, because I get messages like
>
> Error: Cannot install automoc for the archs 'arm64 x86_64' because
> Error: its dependency qt4-mac only
On Apr 1, 2022, at 09:42, Peter West wrote:
> On 1 Apr 2022, at 11:53 pm, Ryan Schmidt wrote:
>
>> On Apr 1, 2022, at 04:32, Peter West wrote:
>>
>>> On 1 Apr 2022, at 7:22 pm, Peter West wrote:
>>>>
>>>> I just tried to insta
On Apr 1, 2022, at 08:52, Christoph Kukulies wrote:
> I’m in the course of installing
>
> sudo port install stlink
>
> The question came to me whether it’s possible to install a specific version
> of the software?
https://trac.macports.org/wiki/howto/InstallingOlderPort
On Apr 1, 2022, at 04:32, Peter West wrote:
> On 1 Apr 2022, at 7:22 pm, Peter West wrote:
>>
>> I just tried to install kmymoney4 on my M1 running 12.2.1. MacPorts spat the
>> dummy with
>>
>> Error: Cannot install kmymoney4 for the arch 'arm64' because
>> Error: its dependency qt4-mac only
On Mar 27, 2022, at 12:48, dan d. wrote:
> Can one delete older python versions then the current python10? Do some
> ports anticipate an older version?
You can uninstall any ports you no longer need or want to have installed. If
any installed ports still declare dependencies on them, MacPorts
On Mar 27, 2022, at 13:06, Richard L. Hamilton wrote:
>
> (although I think Apple provides the servers)
Apple provided the servers from late 2006 [1] (when our first home OpenDarwin
closed its doors) until late 2016 [2] (when Apple's macOS forge service shut
down). Since then, we have used
On Mar 29, 2022, at 09:00, Peter Brommer wrote:
> I somehow managed to shoot myself in the foot with an ill considered forced
> deactivate. A port upgrade outdated command would abort when it tried to
> install libgcc-devel. This must have been a new dependency of one of my
> installed ports
Please direct all mailing list questions to the addresses at
lists.macports.org, not the older addresses that were deprecated in late 2016.
I've fixed the address in this reply.
On Mar 26, 2022, at 04:54, Epstein, David wrote:
> I am using MacPorts base version 2.7.2 under OS 11.6.4.
> All my
On Mar 26, 2022, at 00:48, Michele Venturi wrote:
> As usual this project too is a mess because everyone has a different idea of
> what it is,has been and will be.
If you have constructive criticism for changes that should be made, feel free
to start discussions about them. Otherwise you may
On Mar 23, 2022, at 08:48, Michele Venturi wrote:
> If MacPorts is not a package manager we need one,
> I'd say HomeBrew could be the right tool for the job.
I'm not sure what these remarks are in regards to, but MacPorts was started in
2002 a ports collection [1] based conceptually on FreeBSD
On Mar 18, 2022, at 03:16, VACCARI FRANCO wrote:
> So, is it considered “safe” in MacPorts’ view to update to MacOS 12.3 and
> Xcode 13.3? I remember a warning on the list about this, due to Python 2.x
> removal from Apple
My recommendations posted last month are unchanged.
On Mar 17, 2022, at 21:37, Bill Cole wrote:
> On 2022-03-17 at 17:22:51 UTC-0400 (Thu, 17 Mar 2022 22:22:51 +0100) Tom is
> rumored to have said:
>
>> Hello people, how do I install a python replacement for macOS 12.3?
>
> port install python310 python_select
python_select is a dependency of
On Mar 17, 2022, at 16:22, Tom wrote:
> Hello people, how do I install a python replacement for macOS 12.3?
MacPorts offers many versions of Python. Python 2.7 (/usr/bin/python) was
removed in macOS 12.3. If you want to continue to use Python 2.7, you can
install the python27 port:
sudo port
On Mar 17, 2022, at 11:46, André-John Mas wrote:
> I am having issues installing p7zip on macOS 12.2.1:
It does not appear that you have encountered any problem installing p7zip. Does
p7zip work or no?
> rning: invalid universal_archs configured (should contain at least 2 archs)
In
On Mar 14, 2022, at 10:40, James Secan wrote:
> It is a macOS alias. I use soft links a lot, but only for items that I’m
> accessing when working in a Unix shell.
MacPorts should be able to use your Xcode wherever it is, provided that
`xcode-select -p` shows its path or the path of a symlink
(resending from correct address)
On Mar 13, 2022, at 16:34, Dave Horsfall wrote:
> Smooth as the proverbial baby's bottom on an oldish MacBook Pro, High
> Sierra 10.13.6; well done, all.
>
> I'm quite taken by the progress bar on "cmake"; it keeps changing its
> mind, just like a MacOS
On Mar 12, 2022, at 22:35, Sriranga Veeraraghavan wrote:
> Thank you - I did not know about the port-* manages.
>
> I see from port-reclaim(1) that there are man pages for several other port
> commands, but I didn’t see a reference to these other man pages in the
> port(1) man page. For
On Mar 12, 2022, at 21:57, Richard L. Hamilton wrote:
> Is there a way one can see by examining Portfiles (ideally something that
> could be scanned for with e.g. a perl script), or preferably, with some
> "port" command, which ports require command line tools vs Xcode vs neither
> (albeit
On Mar 10, 2022, at 19:57, Sriranga Veeraraghavan wrote:
> On Mar 10, 2022, at 05:10, Ryan Schmidt wrote:
>
>> "port reclaim --enable-reminders" enables reminders;
>> "port reclaim --disable-reminders" disables them.
>
> Thanks for letting me know ab
On Mar 11, 2022, at 02:02, Michele Venturi wrote:
> What is wrong is that a simple package manager
> requires an entire multigigabyte professional IDE;
> I have even taken the time to talk to them about it
> and file a bug about it,but they clearly don't care...
> It's surely not a new issue,it's
On Mar 10, 2022, at 18:40, James Secan wrote:
> In working my way through my recent “phantom ports” issue I ran the command
> “port diagnose” and was more than a bit surprised by the output line:
>
> Error: currently installed version of Xcode, none, is not supported by
> MacPorts.
>
>
On Mar 10, 2022, at 07:56, Lenore Horner wrote:
>> You could run "sudo port -fv selfupdate" to force MacPorts to reinstall
>> 2.7.2 even though it thinks it already has. If you try that and it
>> experiences some error, let us know.
>
> I did that and it failed but then I remembered that
On Mar 10, 2022, at 03:18, Sriranga Veeraraghavan wrote:
> On Mar 10, 2022, at 00:34, Ryan Schmidt wrote:
>
>> On Mar 9, 2022, at 17:13, James Secan wrote:
>>>
>>> when I run "port upgrade installed -u outdated”
>>
>> This command doesn't mak
On Mar 9, 2022, at 19:55, Lenore Horner wrote:
> Begin forwarded message:
>
>> From: mailer-dae...@yahoo.com
>> Subject: Failure Notice
>> Date: March 9, 2022 at 20:50:45 EST
>> To: lenorehor...@sbcglobal.net
>>
>> Sorry, we were unable to deliver your message to the following address.
>>
>> :
On Mar 9, 2022, at 17:13, James Secan wrote:
>
> when I run "port upgrade installed -u outdated”
This command doesn't make a great deal of sense. You're asking MacPorts to
upgrade the "installed" ports (which includes those those that are outdated and
those that aren't) and also the "outdated"
On Mar 7, 2022, at 08:34, Michele Venturi wrote:
> If I install MPV without Xcode I get an error when I launch it:
>
> dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
> Referenced from: /opt/local/bin/mpv
> Reason: image not found
>
> It's missing something,have you tried to
On Mar 7, 2022, at 08:06, Michele Venturi wrote:
> There is no binary of MPV for OSX 10.13.6? It's too old?
I see a binary of mpv for macOS 10.13:
http://packages.macports.org/mpv/
We produce binaries for Mac OS X 10.6 and later.
Only binaries of default variants are produced. If you are
On Mar 7, 2022, at 06:14, Michele Venturi wrote:
> Web browsers are even more complicated but
> you do not need to install xcode to use safari...
But you do need to install Xcode to *compile* Safari.
In the same way, you need to install Xcode to *compile* mpv, but you do not
need Xcode to
On Mar 7, 2022, at 06:02, Michele Venturi wrote:
> Sadly xcode is needed even for something as simple as
> a media player, for example mpv, I wonder why actually.
Media players are probably extremely complicated pieces of software. Hardly
what I would call simple.
In the case of mpv, it
On Feb 26, 2022, at 12:04, Haren Samarasinghe wrote:
> After reading the installation guide [1], quite a few people that I've
> introduced MacPorts to have thought that a full XCode installation is
> required. They're uncertain of doing this due to the large amount of space it
> requires.
>
On Mar 5, 2022, at 07:29, chilli.namesake wrote:
> On Mar 4, 2022, at 20:39, chilli.namesake wrote:
>
>> https://trac.macports.org/ is refusing to let me submit a ticket returning
>> an inscrutable "invalid parameters" complaint.
That error doesn't immediately ring a bell for me, and since
I noticed copies of the Install macOS Monterey application on both the Catalina
and Big Sur MacPorts buildbot build machines. I've of course never requested
the download of these installers on those systems and they are configured not
to update automatically and not to download new updates
On Feb 13, 2022, at 02:59, Rainer Müller wrote:
>
> On 10/02/2022 13.12, Greg Bell wrote:
>> I'm trying to update yt-dlp (a youtube-dl fork with additional features and
>> fixes)
>>
>> and incurred this…
>> Error: Failed to build graphviz: command execution failed
>>
>> I'm unsure how to
On Feb 19, 2022, at 01:24, rmgls wrote:
> how to bypass the 2.7 python in /system/Library and direct by default to a
> macport version or even a user path.
> details:
> port install scons 3.1.X
> port select --set …..
> invoking scons calls the system scons 2.7?
The scons port version
On Feb 20, 2022, at 11:57, Kirill A. Korinsky wrote:
> The url: https://ports.macports.org/port/gcc10-bootstrap/details/ says that
> port has been deleted.
>
> But it quite alive:
> https://github.com/macports/macports-ports/blob/master/lang/gcc10-bootstrap/Portfile
Bug reports for the ports
On Feb 7, 2022, at 12:52, Bill Cole wrote:
> On 2022-02-07 at 13:16:54 UTC-0500 (Mon, 7 Feb 2022 10:16:54 -0800)
> Watson Ladd is rumored to have said:
>
>> On Mon, Feb 7, 2022 at 9:59 AM Marius Schamschula wrote:
>>>
>>> Watson,
>>>
>>> Compiler?
>>
>> protoc: the thing that takes the
Heads up! For users who want MacPorts to "just work" I recommend not upgrading
to macOS 12.3 (or the beta of it that is already out) for awhile, because it
will remove /usr/bin/python, upon which many ports probably still rely. Stick
with macOS 12.2 or earlier until we've had a chance to notice
On Jan 29, 2022, at 10:56, Richard L. Hamilton wrote:
>
> But looking at the dovecot Portfile, it seems the dependency on apache-solr8
> is specific to the +solr variant (which you have, to be sure). So assuming
> your installation isn't a bit confused somehow, maybe port isn't always smart
>
On Jan 28, 2022, at 15:34, Dave Horsfall wrote:
>
>mackie:~ dave$ echo $DISPLAY
>
>mackie:~ dave$
>
> Is this something I forgot to do during the upgrade? I set $DISPLAY to
> ":0" (an old Unix trick) to no effect,
Setting DISPLAY to :0 is correct on Mac OS X 10.4.x and earlier, but
On Jan 26, 2022, at 08:24, Arno S. Hautala wrote:
> On 25 Jan 2022, at 12:39, paul wrote:
>
>> /usr/sbin/cron
>> /opt/local/bin/bash
>> /opt/local/bin/rsnapshot
>> /opt/local/bin/rsync
>> /opt/local/bin/gcp
>> all have full disk access in system preferences.
I'm not sure if this is it, I've
On Jan 22, 2022, at 10:21, Richard L. Hamilton wrote:
> On Jan 22, 2022, at 11:13, Ryan Schmidt wrote:
>
>> Or are you referring to the date when an update of a portfile was committed
>> to GitHub? If so, why would that be useful to you?
>
> The latter, since the former
On Jan 22, 2022, at 09:36, Richard L. Hamilton wrote:
> I have no idea of the difficulty of such a change, but it would be
> interesting if Portfiles contained a release date, and the database of
> installed ports had both a copy of that for any given installed version, and
> perhaps the
On Jan 22, 2022, at 09:06, Gabriel Rosenkoetter wrote:
>
> On 2022-01-22 09:10 EST, Ryan Schmidt wrote:
>> The use of the "+" character is intentional.
>> "+" means a variant is enabled. "-" means a variant is disabled.
>> "[ ]"
On Jan 22, 2022, at 09:22, Gabriel Rosenkoetter wrote:
>> If we stick with multiple perl versions, and the perl5 port to create the
>> symlinks, then maybe it would indeed help reduce some confusion to change
>> the perl5 port's version to 1.0, or a MMDD date, or anything else that
>> is
On Jan 22, 2022, at 01:15, Gabriel Rosenkoetter wrote:
>
> On 2022-01-22 01:28 EST, Kastus Shchuka wrote:
>> $ port echo installed and perl5
>> perl5 @5.26.1_0+perl5_28
>> perl5 @5.28.3_0+perl5_28
>> perl5
On Jan 22, 2022, at 00:28, Kastus Shchuka wrote:
>
> Please note a clash of terms as there is port action "installed" and port
> pseudo-portname "installed". That is why "port installed" is a valid syntax
> ("installed" is an action here), while "port active" is not. You have to use
> action
On Jan 21, 2022, at 23:32, Gabriel Rosenkoetter wrote:
>
> I think the [+] label, in the output of `port info ` is a confusing
> UI/UX choice, especially in the context of the + as an argument to `port
> install +_version` to request activation of a specific Port
> version.
>
> I think
On Jan 21, 2022, at 22:48, Kastus Shchuka wrote:
> This is for example what I have:
>
> $ port installed and perl5
port installed perl5
"installed" is the command, "perl5" is the list of ports the command will
operate on.
> The following ports are currently installed:
> perl5
On Jan 21, 2022, at 19:43, Gabriel Rosenkoetter wrote:
> I'm… also not sure it's even actually a good idea, since, in my experience,
> Perl is much more flexible about newer versions of `perl` functioning with
> "out-dated" versions of libraries *and* vice versa than, say, PHP is. (I
> think
On Jan 20, 2022, at 22:12, Gabriel Rosenkoetter wrote:
> I didn't have the perl5 port installed on this system at all, just the
> several perl5.xx ports. So I did `sudo port install perl5`.
>
> And that's neat, but:
>
> [58] (gr@wedge:~)% which perl
> /opt/local/bin/perl
> [59] (gr@wedge:~)%
On Jan 20, 2022, at 17:05, Greg Earle wrote:
> Is anyone still using/building on Sierra?
Sure. We still produce binaries for Mac OS X 10.6 and later.
> it tries to build gettext-tools-libs @0.21_0+universal and croaks.
I saw a build failure of one of the gettext subports, might've been
On Jan 16, 2022, at 13:28, phle...@cantab.net wrote:
> Thanks for your brilliantly helpful response.
> Yes.. the pings are indirectly to blame!!
> No, I am not running a third party firewall.
> But I read the notes and noticed the comments about
> changing the max_hosts_to_ping: I had noticed
>
On Jan 13, 2022, at 22:33, chilli.namesake wrote:
>
>> Sometimes we can work around these problems, with or without the developer's
>> help, to get a port working again; other times we can't.
>
> Your explanation is accurate, and though I realize it is easier said than
> done, this shouldn't
On Jan 13, 2022, at 18:27, Manfred Antar wrote:
> gqrx will not build on new version of gnuradio
Then please file a bug report in the issue tracker.
On Jan 13, 2022, at 17:01, Bill Cole wrote:
> On 2022-01-13 at 16:26:01 UTC-0500 (Thu, 13 Jan 2022 15:26:01 -0600) Will
> Senn is rumored to have said:
> [...]
>>
>> My question for y'all goes like this - How long will macports continue to
>> "work" on Mojave?
>
> No one can actually give a
On Jan 9, 2022, at 14:56, Sebastian Flothow wrote:
> I’m using MacPorts on OS X El Capitan 10.11.16, currently kdelibs4 and
> soprano are outdated:
>
> $ port outdated
> The following installed ports are outdated:
> kdelibs4 4.14.3_16 < 4.14.3_17
> soprano
On Jan 3, 2022, at 12:20, Riccardo Mottola wrote:
> how to react best for Let's Encrypt expiration?
https://trac.macports.org/wiki/ProblemHotlist#letsencrypt
On Jan 4, 2022, at 02:52, Christopher Jones wrote:
> Personally, I also occasionally run
>
>> port list requested
>
> to see the list of ports I have actively *requested* to be installed. This
> excludes ports just installed as dependencies of others.
Note that you should use "port installed
1 - 100 of 1365 matches
Mail list logo
