[MacPorts] #47808: port:jpeg proposal to prepare for making port:libjpeg-turbo the default jpeg dependency

MacPorts noreply at macports.org
Sat May 23 03:38:32 PDT 2015


#47808: port:jpeg proposal to prepare for making port:libjpeg-turbo the default
jpeg dependency
--------------------------+--------------------------
  Reporter:  rjvbertin@…  |      Owner:  ryandesign@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:  haspatch
      Port:  jpeg         |
--------------------------+--------------------------

Comment (by cal@…):

 Replying to [comment:4 rjvbertin@…]:
 > The way proposed by this patch is in no way incompatible with the way
 you propose, IMHO it complements it, and makes it less of a "one-shot that
 shouldn't be missed" venture.

 But yet, it is much more complicated than our standard approach of 1.
 replace port, 2. fix dependencies, 3. revbump dependents.


 > Is having an escape route ready if it only builds such an unimaginable
 idea, or even the idea of keeping the original/traditional/reference port
 around such that it can be co-installed with whatever it's going to be
 replaced with?

 No, but it adds significant complexity that we should avoid, IMO. Just in
 the spirit of keeping things simple, where they don't need to be complex.


 > Sometimes I wonder what MacPorts is supposed to be - a show-case what
 FOSS can be installed through it and that's catering to people who'd use
 Arch or Gentoo and spend their computer time keeping the system up to
 date, or something that's aiming to support productivity that's not
 MacPorts-related.

 I believe that most of our users do not directly use libJPEG –
 essentially, most of them probably do not care which specific JPEG library
 is being used, as long as the end result (i.e. their use case of rendering
 or encoding JPEGs) continues to work. And, if due to a change we make,
 this use case becomes faster, that's probably even a welcome side-effect.

 I would even argue that MacPorts should not be a show-case of what FOSS
 can be installed through it, and for that reason '''not''' keep the jpeg
 port around. We should just make a sane choice for most of our users that
 really don't care which JPEG library gets used, just as the big Linux
 distros have done by replacing jpeg with libjpeg-turbo.

-- 
Ticket URL: <https://trac.macports.org/ticket/47808#comment:5>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list