On 11/03/2022 8:02 am, 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 like that by design...
MacPorts is not (just) 'a simple package manager'. Yes, it performs this
function, but first and foremost (and long before we even had binary
tarballs to distribute as a 'package mnager') it is a system for
building packages and their dependencies. To build something you require
a compiler. Many ports will build fine with just the Apple CLT package,
but some indeed require the full Xcode installation in order to be built
(and Xcode also is not just an IDE, but is also a command line build
system).
So yes, if you want to put it in those terms requiring Xcode/CLT is 'by
design'.
Il ven 11 mar 2022, 01:40 James Secan <james.se...@gmail.com
<mailto:james.se...@gmail.com>> ha scritto:
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.
followed by a list of the version supported under my version of
macOS (El Capitan, in this case). Where is port getting this
information? I have Xcode 8.2.0 installed, and none of my attempts
to install ports have run into any trouble related to Xcode not
being installed. I ran "pkgutil -v
--pkg-info=com.apple.pkg.CLTools_Executables” which shows that I
have 8.2.0 installed, and the appropriate MacOSX.sdk files are in
/Library/Developer/CommandLineTools/SDKs. I also tried this on my
test Catalina system, with the same result.
Is something wrong with my ports setup?
Jim
3222 NE 89th St
Seattle, WA 98115
(206) 430-0109
> On Mar 10, 2022, at 12:34 AM, Ryan Schmidt
<ryandes...@macports.org <mailto:ryandes...@macports.org>> wrote:
>
> 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" ports (those that are outdated). It would be simpler and
more efficient to just run "sudo port -u upgrade outdated".
Single-dash/single-letter flags like "-u" go after "port" and before
the action (the action in this case being "upgrade").
>
> For completeness, "-u" means "uninstall inactive ports"; if you
want to keep inactive ports, for example as a safeguard so that you
could return to them in case something is wrong with the new
version, then don't use "-u". When you eventually run "sudo port
reclaim", that will get rid of the inactive versions.
>
> MacPorts reminds to run "sudo port reclaim" if you have not done
so in a few weeks, unless you have configured MacPorts not to remind
you.