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.
In article <[EMAIL PROTECTED]> Bill Mitchell <[EMAIL PROTECTED]> writes:
> > 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 prac
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 fa
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
4 matches
Mail list logo
