[MacPorts] #25454: umbrello

[MacPorts]

#25454: umbrello
-----------------------------------------+----------------------------------
  Reporter:  bertrand.zuchuat@…          |       Owner:  snc@…           
      Type:  request                     |      Status:  closed          
  Priority:  Normal                      |   Milestone:                  
 Component:  ports                       |     Version:  1.9.1           
Resolution:  fixed                       |    Keywords:                  
      Port:  kdesdk4                     |  
-----------------------------------------+----------------------------------

Comment(by snc@…):

 Replying to [comment:11 ryandesign@…]:
 > Jeremy, the patchfile can be deleted now, right? since the port isn't
 using it anymore?

 It's already deleted.

 > I still wonder about the variant name and its description.
 > I would have preferred something like: `variant boost description {Use
 Boost (required to build Umbrello)}
 > Does adding Boost to the build serve any purpose ''other'' than enabling
 the build of Umbrello? If not, would "umbrello" be a better/clearer
 variant name choice?` variant umbrello description {Build Umbrello}`

 I'll happily entertain changing the description.

 Umbrello itself uses more than just boost but it's the only thing I block
 in the dependency tree because it can be such a pain to build. I generally
 follow the kitchen sink perspective except for when a painful build is
 involved. It's along this line that I decided to use package names for
 variants, like `x11` and `qt4`: it's to avoid building the package across
 all installs. An argument can also be made for granular control of what is
 built. Do you think it's more important to aid a user from installing a
 package or making variants reflect precisely what they do?

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