In article [EMAIL PROTECTED] you wrote:
: We should document what we ship as we ship it.
: No argument, but that implies lots of work for maintainers
: when initially building packages and when upgrading to new
: upstream releases. I'm not sure that it's practical.
I think it's necessary. If
Bill Mitchell:
In my own packages, I've been trying to provide debianized docs
which change references to /usr/local to just plain /usr where it's
clear from the context that this would be incorrect on a debian
system. I've come to think that even this amount of twiddling the
Bill Mitchell writes (Bug#1887: cfengine 1.2.14-2: documentation errors):
In my own packages, I've been trying to provide debianized docs
which change references to /usr/local to just plain /usr where
it's clear from the context that this would be incorrect on
a debian system. I've come
On Thu, 23 Nov 1995, Ian Jackson wrote:
We should document what we ship as we ship it.
No argument, but that implies lots of work for maintainers
when initially building packages and when upgrading to new
upstream releases. I'm not sure that it's practical.
Some quick grepping around in my
On Wed, 22 Nov 1995, Chris Fearnley wrote:
The info documentation included refers to /usr/local/bin/cfengine when
Debian's cfengine is installed in /usr/bin/cfengine.
I'm closing this without action.
I've looked at the cfengine info files, and I think it's clear
from the context that the
5 matches
Mail list logo
