On Wednesday 26 January 2011 09:27:10 Ralf Lang wrote:
are there any objections to moving pear packages (which are quite a lot) from server:php:applications to a new sub project server:php:applications:pear
What are the benefits you forsee in doing this? If there are clearly demonstrable benefits then I might be in favour of it.
Would you search for a bunch of common libraries in something called application?
Except PEAR pear packages can, and in fact are, sometimes more than just libraries. Applications get bundled using pear channels too. phpDocumentor, php codesniffer are two that immediately spring to mind. How would you make the distinction between something like phpDocumentor & php codesniffer (both applications) and something else which is clearly a libary? Do we then search for applications in s:p:applications except if we remember the applcation might be in pear? What about other utilities/apps/libaries that may be bundled with an installble pear channel? I feel this is going to lead to confusion I don't see any immediate benefit from this. -- “What can be asserted without proof can be dismissed without proof.” - Christopher Hitchens -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org