> From: Steve Greenland <[EMAIL PROTECTED]>
>
> On 22-Aug-00, 23:12 (CDT), Daniel Barclay <[EMAIL PROTECTED]> wrote:
> > ...
>
> ... Current policy
> requires that /usr/doc/ exist (possibly as a symlink to
> /usr/share/doc/).
Then why don't mo
rams (the Start Menu subfolder), and also gives you a
starting point (the read-me file) for using the software.
I'm certainly not saying that Debian should use those methods
or anything close (besides, they wouldn't work for installing
multiple packages at once); I'm
all one thing at a
time, and where it can leave a Start Menu folder open on your desktop
to give you a hint about what new commands you can run. (Not that
that's a _good_ orientation or pointer, but it's something.)
Daniel
--
Daniel Barclay
[EMAIL PROTECTED]
(Hmm. A l
f, Debian versions also need some kind of
README.Debian file to describe what Debian-specific changes were made
to the package (so you know what doesn't work according to the upstream
manual pages, README files, or other documentation).
Daniel
--
Daniel Barclay
[EMAIL PROTECTED]
(Hmm.
info
> pages, man pages, web site, whatever).
Yes, please! With many packages, when you install them, you have no
known starting point for finding out what capabilities (commands,
daemons, etc.) you just installed, or what to do to configure them.
Daniel
--
Daniel Barclay
[EMAIL PROTECT
> From: Anthony Towns
> What's wrong with using README.Debian for this purpose, which is already
> in common use?
Probably nothing, except that it isn't used consistently.
Daniel
Could you all please consider this suggestion for a standard
post-installation read-me file?
This is something I was reminded of on the Debian-Java list:
--- Start of forwarded message ---
...
Date: Thu, 9 Sep 1999 00:16:39 -0400 (EDT)
From: Daniel Barclay <[EMAIL PROTECTED]>
7 matches
Mail list logo
