[Pidgin] #2883: Not a bug, yet still a HUGE pain: no binary installed

[Pidgin]

#2883: Not a bug, yet still a HUGE pain: no binary installed
---------------------------+------------------------------------------------
  Reporter:  bezeek        |       Owner:        
      Type:  defect        |      Status:  closed
  Priority:  minor         |   Milestone:        
 Component:  pidgin (gtk)  |     Version:  2.1.1 
Resolution:  invalid       |    Keywords:        
   Pending:  0             |  
---------------------------+------------------------------------------------
Changes (by deryni):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 I know exactly what portage is and I know what it does. What I'm trying to
 tell you is that the results of the build are *entirely* up to what you
 the user specify and what the ebuild script does. We control *neither* of
 those things. If you think the ebuild should tell you at the end which of
 the clients it built that's fine, get the Sabayon/gentoo maintainer to do
 that to the ebuild. In fact the pidgin configure script *does* tell you at
 the end of its output which of the two interfaces it is going to build,
 which protocols it will build, which ssl plugins it will build, and what
 other features are turned on or off. Neither the fact that the ebuild
 ignores this message nor that you didn't look for it in the build log is
 our fault.

 As to splitting up the package that is again almost entirely up to your
 distribution, because in fact if they wanted to have separate ebuilds with
 'hard' dependencies they could.

 I am going to close this ticket because nothing here has anything to do
 with us. More to the point even, the ebuild *explicitely* tells you not to
 report bugs to us first but to go through gentoo first. Or at least the
 gentoo ebuild does, if Sabayon has their own and it doesn't I think it
 should be added there as well.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/2883#comment:3>
Pidgin <http://pidgin.im>
Pidgin