On Mon, 21 Jun 1999, Chris Lawrence wrote:
> In that vein, perhaps the best policy is to not require the package
> maintainer to file a bug report himself/herself.
This part was changed in my new version:
If no manual page is available, this is considered as a bug and
should be reporte
On Jun 21, Chris Waters wrote:
> I think that the old policy of using undocumented(7) made it too easy
> for people to ignore the requirement to have a *real* man page, and I
> think this proposal (without editorial commentary) will go a long way
> toward addressing that issue, since undocumented(7
Joey Hess <[EMAIL PROTECTED]> writes:
> Wow! You've utterly bypassed the whole policy issue with a brilliant idea!
Well, no (though that was my first reaction too). We still should
have a policy regarding the *default* menu layout, and it still makes
sense to have it separate from the menu packa
Chris Lawrence <[EMAIL PROTECTED]> writes:
> I would be willing to support this proposal with the following
> additional sentence included:
> "It is not very hard to write a manual page; see the example manual
> page provided by dh_make for a template."
I disagree (mildly). Policy should state
Je 1999/06/20(0)/13:06, Edward Betts montris sian geniecon skribante:
> On debian-policy, joost witteveen <[EMAIL PROTECTED]> wrote:
> > Hi there,
> >
> > I've just released menu-2.0. It has many new features, one of
> > wich is the automatic optimization of the menu tree, using
> > something I'v
Je 1999/06/19(6)/23:06, Richard Braakman montris sian geniecon skribante:
> joost witteveen wrote:
> > forcetree
> > Apps/Sound
> > endforcetree
>
> Is it also possible to specify that a menu (such as Apps) must have only
> submenus? Mixed menus seem cluttered and I find them hard to use.
At t
Je 1999/06/20(0)/12:06, Joseph Carter montris sian geniecon skribante:
> On Sun, Jun 20, 1999 at 02:50:51PM -0300, Nicolás Lichtmaier wrote:
> > > Would it be possible to group menu items that would be together, just do
> > > not
> > > put them in the menu? So my menu would become:
> > >
> > > Ap
On Jun 21, Roland Rosenfeld wrote:
> On Sun, 20 Jun 1999, Chris Lawrence wrote:
>
> > I would be willing to support this proposal with the following
> > additional sentence included:
> >
> > "It is not very hard to write a manual page; see the example manual
> > page provided by dh_make for a tem
On Sun, 20 Jun 1999, Chris Lawrence wrote:
> I would be willing to support this proposal with the following
> additional sentence included:
>
> "It is not very hard to write a manual page; see the example manual
> page provided by dh_make for a template."
I fully agree with the first part of thi
On Jun 20, Chris Waters wrote:
> Yes, this seems like a reasonable and satisfactory proposal, I will second.
I would be willing to support this proposal with the following
additional sentence included:
"It is not very hard to write a manual page; see the example manual
page provided by dh_make fo
-BEGIN PGP SIGNED MESSAGE-
Yes, this seems like a reasonable and satisfactory proposal, I will second.
-BEGIN PGP SIGNATURE-
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.5.1, an Emacs/PGP interface
iQCVAwUBN22HMzZs0/7rwRsBAQFdwgQAkBrgDrQADdPjLKEMBq/U28ejCwMVD
Package: debian-policy
Version: 2.5.1.0
In the /dev section of the FSSTND
(/usr/doc/debian-policy/fsstnd/fsstnd-1.2.txt.gz) the following text is
found: ``All device special files should follow the standard in that
document, which is available via anonymous ftp at ftp.yggdrasil.com
in /pub/device
12 matches
Mail list logo
