On Fri, Jan 28, 2000 at 05:41:55PM -0600, Manoj Srivastava wrote:
> I think I tend to disagree here. I really expect more of a
> debian developer than a glorified bureaucrat -- we are trying to
> create the best free distribution, and that often entails making the
> package *better* than
>>"Owen" == Owen Dunn <[EMAIL PROTECTED]> writes:
>> What I'm really trying to say is that what we should expect from a
>> maintainer is _commitment_.
Owen> As I've understood it, the only thing that has really been
Owen> required in the past of a maintainer (beyond any initial
Owen> packagi
On Tue, Jan 18, 2000 at 02:13:57AM +, Matthew Vernon wrote:
> It's tricky to write a decent manpage if you know no nroff.
Counter example: the sashconfig man page from the sash package.
The source package contains no roff for this manpage.
A one-liner in debian/rules generates the roff.
--
On Tue, Jan 18, 2000 at 01:00:11PM +0100, Roland Rosenfeld wrote:
> On Tue, 18 Jan 2000, Matthew Vernon wrote:
>
> > It's tricky to write a decent manpage if you know no nroff.
>
> You don't have to learn all the nroff macros to write a simple man
> page! Have a look at the manpage-HOWTO
> (http
On Tue, 18 Jan 2000, Matthew Vernon wrote:
> It's tricky to write a decent manpage if you know no nroff.
You don't have to learn all the nroff macros to write a simple man
page! Have a look at the manpage-HOWTO
(http://www.schweikhardt.net/man_page_howto.html) or man(7) and you
will see, that yo
Matthew Vernon <[EMAIL PROTECTED]> writes:
> It's tricky to write a decent manpage if you know no nroff.
Not that tricky -- I managed. :-)
Didn't seem any harder than, say, creating a debian control file. In
fact, given how much documentation I've had to read about debian
control files vs man
On 17-Jan-00, 15:42 (CST), Richard Braakman <[EMAIL PROTECTED]> wrote:
> Indeed. Consider, though, that writing a small manpage that points
> at existing documentation is not onerous.
Which is why I said that such a man page should be encouraged :-). In
fact, given a decent template (many of wh
Richard Braakman writes:
> Indeed. Consider, though, that writing a small manpage that points
> at existing documentation is not onerous. It is about as hard as
> figuring out how to create a menu entry. I think it's part of the
> packaging process.
It's tricky to write a decent manpage if
On Sun, Jan 16, 2000 at 01:11:44PM -0600, Steve Greenland wrote:
> It is not the job of the Debian maintainer to write the upstream
> package. The job of the Debian maintainer is to package the
> existing upstream package in a form convenient for Debian users in
> a way that is complementary to th
On 13-Jan-00, 16:39 (CST), Richard Braakman <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 13, 2000 at 12:01:33AM +, Ian Jackson wrote:
> > Richard Braakman writes ("Re: policy summary"):
> > > Frankly, I like the idea. I think packages are being created far too
> > > lightly these days. Writing a
(I inadvertently sent this to -devel earlier, so apologies to anyone
already having read it there.)
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
> What I'm really trying to say is that what we should expect from a
> maintainer is _commitment_.
As I've understood it, the only thing th
On Thu, Jan 13, 2000 at 12:01:33AM +, Ian Jackson wrote:
> Richard Braakman writes ("Re: policy summary"):
> > On Sun, Jan 09, 2000 at 09:38:17PM +, Matthew Vernon wrote:
> > > OTOH, new packages with lintian errors tend to get rejected - it would
> > > be unfair to reject new software simp
12 matches
Mail list logo
