Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#350051: rt2500-source: installs files in wrong places,
which was filed against the rt2500-source package.

It has been closed by one of the developers, namely
Aurelien Jarno <[EMAIL PROTECTED]>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.



tar
make
make install

leaves you with an alias in /etc/modprobe.conf , instead
of somewhere within /etc/modprobe.d , as I believe  it should.
Also, the compiled rt2500.ko module is left in
/lib/modules/2.6.12/extra/rt2500.ko instead of somewhere
below /lib/modules/2.6.12-1-686/ as it should.
Consequently, modprobe does not find the module,
and nothing functions.


This is because you are not using the Debian way to build the modules. Please have a look at /usr/share/doc/rt2500-source/README.Debian

Granted.   However a note to that effect should be included
somewhere obvious.     For instance, when you run

make install

it should echo "Debian does not use make install. Please see /usr/share/doc/rt2500-source/README.Debian"

All documentation should be as local as possible,
and there should be pointers to the documentation from wherever
people will be looking. It's really
not quite appropriate to have a directory that gives incorrect
installation instructions without even a note that there are
distribution-specific instructions.

I did indeed look at /usr/share/doc/rt2500-source/README.Debian
after the fact.   It was quite helpful, but it still leaves
a documentation bug: the lack of a pointer to the relevant
documentation from the source directory.

I know, someone will say "But you should always look at
/usr/share/doc/*/README.Debian!"    That's correct,
but the wrong attitude:  that's the attitude of a
Debian expert.    Real computer systems need to be
designed for people who aren't Debian experts,
because there are 6 billion of them and a few thousand
experts.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to