[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#484674: mldonkey: Packaging too complex

Package: mldonkey
Severity: normal

mldonkey packaging is way to complicated and bloated.  This is
unnecessary and causes bugs.

 * Why does mldonkey-server need an init script?  Yes, it's a daemon,
   but that is merely an implementation detail.  When it comes down to
   it, mldonkey is a *p2p client*.  It should be run by normal users
   when they want to connect to a p2p network.

 * Why so many debconf questions?

 * Why all of the Debian-specific utilities in debian/utils?  This is
   just vanity.  Please, ship the upstream software, not your own.

 * Why the special make invocations?  The configure script suggests
   running `make', but debian/rules runs `make utils opt' or some such
   nonsense.  It fails when I try to build the version from intrepid on
   my hardy box (after backporting and installing the dependencies),
   even though just plain `make' runs perfectly.

All of these things make the package much more complicated than it
should be.  Simply trying to backport the package is a process that
takes several hours.

What is the justification for all of this complexity?

-- System Information:
Debian Release: lenny/sid
  APT prefers hardy-updates
  APT policy: (500, 'hardy-updates'), (500, 'hardy-security'), (500, 'hardy-backports'), (500, 'hardy'), (500, 'gutsy')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-14-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Forest Bond

Attachment: signature.asc
Description: Digital signature

Reply to: