On Thu, 2005-07-07 at 14:39 +0200, martin f krafft wrote:
> Sure. But I am talking about changes. Those are not made and then
> everyone is expected to abide by them. Instead, they are catalysed
> from common and proven strategies.
True enough. But read the statement of the fact that policy maint
also sprach Ian Campbell <[EMAIL PROTECTED]> [2005.07.07.1501 +0200]:
> I don't think that having policy be determined by existing practises and
> forcing maintainers to follow it are mutually exclusive.
>
> Once a strategy is common and proven it enters policy, at which point it
> becomes compuls
On Thu, 2005-07-07 at 14:39 +0200, martin f krafft wrote:
> also sprach Michael Weyershäuser <[EMAIL PROTECTED]> [2005.07.07.1431 +0200]:
> > I guess you were refering to chapter 6 of the Developers Reference,
>
> No, I was refering to the policy.
>
> > "Best packaging practices", or something li
> Sory that you get the mail twice now, martin, I accidentally sent
> the first one to you instead of the list -.-
Here's my (also) personal reply:
also sprach Michael Weyershäuser <[EMAIL PROTECTED]> [2005.07.07.1431 +0200]:
> I guess you were refering to chapter 6 of the Developers Reference,
martin f krafft wrote:
>Uh, isn't the Debian policy a document for existing practices,
>rather than a vehicle to force maintainers down a certain road?
>
>
>
"Debian Policy Manual
Abstract
This manual describes the policy requirements for the Debian GNU/Linux
distribution. This includes th
also sprach Branden Robinson / Debian Project Leader <[EMAIL PROTECTED]>
[2005.07.07.0836 +0200]:
> The power of the maintainers of the Debian Policy Manual is
> substantial; they have the power to mandate standards of behavior
> for Debian packages, and a significant change to Debian Policy can
>
6 matches
Mail list logo
