[MacPorts] #74380: Installing 'nano' takes a "long time"

[MacPorts]

#74380: Installing 'nano' takes a "long time"
--------------------------+--------------------
 Reporter:  seamusdemora  |      Owner:  (none)
     Type:  request       |     Status:  new
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:  2.12.6
 Keywords:                |       Port:  nano
--------------------------+--------------------
 I don't want this to sound like a complaint, but I'm very curious about
 why there are no pre-compiled ports for (what I imagine are) common
 utilities. My system is a 2019 MBP running Tahoe... I'm using this MBP as
 a "project" computer, and so I "cleaned" it, and upgraded the OS to Tahoe.
 Immediately after installing MacPorts, I wanted to install 'nano' to avoid
 Apple's 'pico'...

 Here's how it went:

 {{{
 % sudo port install nano
 --->  Computing dependencies for nano
 The following dependencies will be installed:
  autoconf
  automake
  bzip2
  gettext
  gettext-runtime
  gettext-tools-libs
  gperf
  libiconv
  libmagic
  libtextstyle
  libtool
  lz4
  m4
  ncurses
  xz
  xz-bootstrap
  zlib
  zstd
 }}}

 In addition to compiling 'nano', each and every dependency (19 of them)
 also had to be "built". This required 336 lines of output, and 32 mins, 54
 seconds of build time. That's quite a lot to get nano - at least it seems
 so to me.

 Can someone explain why virtually nothing is available as a compiled
 package?  Is it the age of my Mac (2019)?  Am I making some stupid mistake
 in installation?  Something else?  I've been using MacPorts for years -
 and I really like it - but it does seem that the availability of pre-
 compiled apps has fallen off dramatically since I started using
 MacPorts???

-- 
Ticket URL: <https://trac.macports.org/ticket/74380>
MacPorts <https://www.macports.org/>
Ports system for macOS