Re: What's a correct naming scheme for PHP extensions (written on compiled language, e.g. C)?
- To: debian-webapps@lists.debian.org
- Subject: Re: What's a correct naming scheme for PHP extensions (written on compiled language, e.g. C)?
- From: Sergey B Kirpichev <skirpichev@gmail.com>
- Date: Tue, 8 Mar 2011 14:14:25 +0300
- Message-id: <AANLkTi=E_VN8csKBadL7KNTRbwTZnSY2d6EkCcpBoEyL@mail.gmail.com>
- In-reply-to: <1299566548.21613.27.camel@minnika>
- References: <AANLkTikrZoofwRf238EXvc3jkEaSbW1N3E9VQVK9qTS=@mail.gmail.com> <20110222104443.GA32057@cobija.connexer.com> <20110302202641.GA18599@darkstar.order.hcn-strela.ru> <1299566548.21613.27.camel@minnika>
On Tue, Mar 8, 2011 at 9:42 AM, Sean Finney <seanius@debian.org> wrote:
> Well it's not a "policy violation" in the sense that the PHP Policy
> Draft is not actually Debian Policy, but the draft for a set of
> recommendations.
Anyway, you got an idea.
> It also seems that the draft is... well... ambiguous
> enough on a few points that it's not read the same way by different
> packagers.
>
> yes i would agree that if it's a pre-compiled pecl module that phpN-pkg
> is more appropriate, but it's nothing I'd shed any tears over since it
> is fairly inconsistent already.
Hope, it's time to fix this. I'm also surprised why
Debian PHP Maintainers are outside of this
policy creation process.
Where I can find source (SGML or whatever) of this policy document?
Reply to: