Re: [MacPorts] #74362: port 2.12.6 does not build on PPC Leopard, Mac OS X 10.5.8, because of error: ‘CURLOPT_NOPROXY’ undeclared (first use in this function)

[MacPorts]

#74362: port 2.12.6 does not build on PPC Leopard, Mac OS X 10.5.8, because of
error: ‘CURLOPT_NOPROXY’ undeclared (first use in this function)
------------------------+-----------------------------
  Reporter:  ballapete  |      Owner:  (none)
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:  MacPorts Future
 Component:  base       |    Version:  2.12.6
Resolution:  fixed      |   Keywords:  leopard
      Port:  port       |
------------------------+-----------------------------

Comment (by fhgwright):

 Replying to [comment:10 ballapete]:
 > Replying to [comment:9 fhgwright]:
 > If your ports tree is new enough to include the `MacPorts` port with the
 patch, then what I suggested above should work, and then things should
 work normally afterward.
 > {{{
 > MacPorts                       @2.12.5         sysutils/MacPorts
 > }}}
 >
 > cannot not help much…
 >
 >   If your ports tree is too old, you may have to do a `port sync` first
 to get the updated `MacPorts` port.
 > >
 > > Admittedly, this requires using `port sync`,
 >
 > Which would wipe out all my adaptations of some `Portfiles`:
 [...]

 What???  You're using a git tree as your primary ports tree ''and''
 relying on a ton of uncommitted changes?  You really ''are'' asking for
 trouble, aren't you?

 Using a git tree as the primary ports tree is a bad idea because git
 trashes mtimes, and incremental portindex relies on correct mtimes.  Since
 one needs to rerun portindex every time one sneezes, requiring it to
 reindex the entire ports tree is horrible.  Unless and until incremental
 portindex is fixed to play nicely with git, the only reasonable git
 involvement is to use it to construct a sparse ports-tree overlay
 containing just the modified ports, with the remainder coming from the
 usual source.  There are a couple of gotchas with this arrangement, but it
 mostly works pretty well.

 Relying on uncommitted changes on a long-term basis is also a really bad
 idea.  Git commits and branches are lightweight and easily created; use
 them liberally.  You can always rearrange them later.  Any change that
 remains uncommitted for more than a day is a mistake.

 Replying to [comment:11 ballapete]:
 > Trying to build with port, i.e. `port install MacPorts`, when `Portfile
 and its patch file` are from an up-to-date Mac leads to:
 >
 > {{{
 > Error:
 > Error: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 > Error: !! DO NOT INSTALL THE MACPORTS PORT !!
 > Error: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 > Error: The MacPorts port is only used to build the installers you can
 download from
 > Error: macports.org It is not intended for installation by a user, and
 doing so will
 > Error: overwrite your MacPorts installation and render it unusable when
 removed.
 > Error:
 > Error: Failed to activate MacPorts: Installation aborted
 > Error: See /opt/local/var/macports/logs/_Volumes_BSD-Linux_MacPorts-
 Ports_sysutils_MacPorts/MacPorts/main.log for details.
 > Error: Follow https://guide.macports.org/#project.tickets if you believe
 there is a bug.
 > Error: Processing of port MacPorts failed
 > }}}
 >
 > So technical K.O. for Leopard?

 Read what I wrote again.  I never said to use `port install`; I said to
 run `make install` from the appropriate directory in the build tree, which
 is not the same thing.  And of course this has to be on the machine in
 question; running it on a different machine doesn't help.

 BTW, it appears that it's OK to rerun the package installer over an
 existing installation, but don't take my word for it without a good
 backup.

-- 
Ticket URL: <https://trac.macports.org/ticket/74362#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS