Re: fastlink_4.1P-fix88-1_i386.changes is NEW (fwd)

[Andreas Tille <tillea@rki.de>]

On 16 Apr 2003, Elizabeth Barham wrote:

> I've concluded that the manpage is not the correct place for
> describing such a lengthy line of data.
Perhaps we might just ship the whole web page or at least a link to it.
(In general I prefere ro provide *good* documentation inside the packages
for offline reading.)

> ...
> which means, among other things, that they hardcoded some of the
> variables which, I guess, could have been passed in on the command
> line.
I've got the same impression when browsing quickly through the README
files.  One of them seem to explain how to set some parameters at compile
time - but I was not really able to believe that they could not been
overriden at run time.

>    Is dealing with this sort of thing our job?
I think it is on behalf of Debian to provide good software.  Depending
on your skills there are 3 ways:

   1. Just file a bug report against fastlink using the reportbug
      utility.  Tag it wishlist and describe the problem.

      The result would be that I have to care for forewarding this stuff
      to upstream, because I definitely have no time to fix this.

   2. Do the same as above and tag it "patch" while providing a patch
      which just fixes the problem.

      This would be great because it would speed up the solution for
      the problem for Debian users drastically.

   3. Just send the patch upstream and ask them for inclusion (perhaps
      also doing step 2. and tell upstream that the famous ;-) Debian
      GNU/Linux distribution would ask for this feature).

      This would reduce the amount of work for me to a minimum because
      it is my duty as maintainer to care for the quality of the
      package.

Thanks for your cooperation

          Andreas.
--
Mankind must put an end to war before war puts an end to mankind.
John F. Kennedy