[MacPorts] #42256: grilo @0.2.7 new Portfile

[MacPorts]

#42256: grilo @0.2.7 new Portfile
-------------------------+----------------------
  Reporter:  juanrgar@…  |      Owner:  devans@…
      Type:  submission  |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:  fixed       |   Keywords:
      Port:  grilo       |
-------------------------+----------------------

Comment (by devans@…):

 I'm not enthusiastic about it. :-)

 I'm thinking that the point of grilo is to create a uniform API that
 allows other apps to access a large variety of content providers without
 having to worry about the provider specific details.  So I would enable
 all the working plugins by default and only use a variant if a plugin has
 problems or could be considered experimental by the upstream developers
 (not ready for prime time as it were) or if they conflict with one
 another.

 Minimizing the number of variants is usually the best policy since in the
 current state of things, MacPorts doesn't allow dependents to request a
 particular variant so you have to be sure that all functionality required
 by them is built in the default configuration.  Having a default variant
 only makes sense in the conflict situation (e.g. +x11 vs +quartz,
 +python26 vs +python27) or there is a reason that you want to allow the
 user to disable the variant for some reason.

 Simple is better, IMHO.

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