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 ballapete):

 Replying to [comment:14 fhgwright]:
 > Replying to [comment:13 ballapete]:

 > Git isn't just for collaboration - it also helps keep track of your own
 changes, and allows you to pick and choose which ones you want to include
 at any given time.
 >
 I know that it's not just collaboration. If I would commit my changes
 (needing a permit first) all MacPorts users would receive them and would
 get a faulty set of Portfiles. Because my changes are too specific for me
 and Leopard. And they do not use if's to make a difference between
 hardware and software versions. They are kind of private, preventing me
 from becoming a zoo keeper of Pythons. And Pearls.

 > > OK, tomorrow trying `make install`. I assumed the "make" was a typo –
 when port starts why should make finish? (Because of patch phase?)
 >
 > If I'd meant `port install`, why would I have included the `cd`?

 That puzzled me too…

 > > Tomorrow… (with 13 hours of sunshine again, and maybe knowing then
 what "the package installer" is)
 >
 > The package installer is what you download from the MacPorts website to
 get started.

 This happened some decades ago…

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