[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#30036: marked as done ([OLD PROPOSAL] Including subpolicies (emacs, menu etc) in policy)



Your message dated Wed, 13 Jun 2001 13:16:54 -0500 (CDT)
with message-id <20010613181654.5AFED470E@speedy.private>
and subject line Bug #30036:
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Nov 1998 19:42:49 +0000
Received: (qmail 27197 invoked from network); 26 Nov 1998 19:40:14 -0000
Received: from pizarro.unex.es (root@158.49.8.2)
  by master.debian.org with SMTP; 26 Nov 1998 19:40:14 -0000
Received: from guadiana.unex.es (root@guadiana.unex.es [158.49.8.233])
	by pizarro.unex.es (8.8.5/8.8.5) with ESMTP id UAA04926
	for <submit@bugs.debian.org>; Thu, 26 Nov 1998 20:39:48 +0100
Received: from cantor.unex.es (sanvila@cantor.unex.es [158.49.18.105])
	by guadiana.unex.es (8.8.5/8.8.5) with SMTP id UAA30728
	for <submit@bugs.debian.org>; Thu, 26 Nov 1998 20:39:47 +0100
Date: Thu, 26 Nov 1998 20:39:13 +0100 (CET)
From: Santiago Vila <sanvila@unex.es>
To: Debian Bugs <submit@bugs.debian.org>
Subject: debian-policy could include emacs policy
Message-ID: <Pine.LNX.3.96.981126203608.7142A-100000@cantor.unex.es>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Package: debian-policy
Version: 2.5.0.0
Severity: wishlist

5.8 Emacs lisp programs

   Please refer to the `Debian Emacs Policy' (documented in
   debian-emacs-policy.gz of the emacsen-common package) for details of
   how to package emacs lisp programs.

Would there be any objection to including the content of
debian-emacs-policy.gz into the policy itself, instead of this reference?

Thanks.

-- 
 "9ac42dfe48c8686fd52e053c72dd67e7" (a truly random sig)

---------------------------------------
Received: (at 30036-done) by bugs.debian.org; 13 Jun 2001 18:16:58 +0000
>From steveg@molehole.dyndns.org Wed Jun 13 13:16:57 2001
Return-path: <steveg@molehole.dyndns.org>
Received: from 206.180.143.9.adsl.hal-pc.org (speedy.private) [::ffff:206.180.143.9] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 15AFCK-0003U5-00; Wed, 13 Jun 2001 13:16:56 -0500
Received: by speedy.private (Postfix, from userid 1000)
	id 5AFED470E; Wed, 13 Jun 2001 13:16:54 -0500 (CDT)
To: 30036-done@bugs.debian.org
Subject: Re: Bug #30036:
Message-Id: <20010613181654.5AFED470E@speedy.private>
Date: Wed, 13 Jun 2001 13:16:54 -0500 (CDT)
From: steveg@molehole.dyndns.org (Steve Greenland)
Delivered-To: 30036-done@bugs.debian.org

This note is being sent as part of a project to clean out old (> 1yr)
debian-policy proposals. If you disagree with action below please
respond to bug#@bugs.debian.org, not to me, so that the discussion may
be carried out publically in debian-policy. Feel free to re-open the
bug while it's being discussed -- I'm not trying to force any
particular disposition, just taking my best shot at resolving dead
issues.


Bug#30036: Including subpolicies (emacs, menu etc) in policy

Summary: Proposed incorporating subpolicies into policy
document. Nobody seemed to like this much; a counter-proposal of
including the subpolicy docs in the debian-policy .deb gained more
support. Lots of concern about mixing of technical details (e.g. how
to write a menu-method) with policy (e.g. what is the menu heirarchy).

Discussion: This seems to have come to consensus and agreement, as the
policy .deb currently contains mime-policy, menu-policy, and
perl-policy. No emacs-policy, but I'd guess that audience is small
enough there's no problem there. Presumably subpolicy writers will
submit their doc when it seems appropriate.

Action: close.



Reply to: