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

Pidgin trac at pidgin.im
Fri Aug 31 12:37:39 EDT 2007


#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             |  
---------------------------+------------------------------------------------
Comment (by bezeek):

 I'm sorry if I downplayed your knowledge of Portage. Many Linux users I've
 spoken to seem to think it's some sort of magic gun shooting silver
 bullets.

 My point however is not about Portage, or any specific distribution for
 that matter. I pointed out that when using any package manager (in my
 experience) the installation will not pause for the user to read any
 warnings, only halt on an error or print output at the very end of the
 make install. Simply determining and echoing which binary exists at the
 end of installation would place said message at the end of the build log,
 where it could be read.

 As far as my comment on splitting the packages goes, I was referring to
 the source packages, which would prompt package maintainers for all
 distributions to update their releases accordingly.

 And for why I ran into the problem, that's not just me. All in all, the
 point is that it is up to the software developers to make the software as
 friendly as humanly possible, not to just wave off obsticles expecting
 someone else to make a change.

 For the record though, any user running a distribution without GTK
 installed could have easily run into the problem without using software
 that automatically resolves dependancies. This would be any of the actual
 binary package installers that you refer to, as opposed to their package
 management backends (i.e. dpkg as opposed to apt, or compiling from
 source, for those so unfortunate to download the tarball from this
 website.)

 It may not be your fault, but that doesn't mean you can't fix it (in well
 under an hour even.)

 And I'm not speaking for me - I'm not the only one with this problem, or
 this distribution.

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


More information about the Tracker mailing list