Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[buckminster-dev] Re: Enhancing buckminister for php

Hi Atul,

Atul SIngh wrote:
Hi guys
I am thinking about possible enhancements that I can do to improve the
appeal of buckminister to the php community.
>
That sounds like a great idea! We've been thinking about that domain too (it's a big one) but to be honest, neither of us have done much php development. If you know this domain and want to help us with it it would be super.

To my understanding pear and
pecl (c extensions) are popular repositories for php extensions. Is there
any other extension anyone is aware of that I should target ?

I guess CPAN would be another repository of great interest to that community. Or does CPAN contain pear and pecl packages (as you can see, I'm a complete illiterate here)?

pear packages can be easily installed on both windows and linux by using
pear command line interface (cli). pecl packages can be easily installed on
linux by using yum or apt-get.

I can use the information in pear and pecl packages to generate a cspec. I I
am confused whether I can simply invoke the pear/apt-get/yum command from
inside buckminister to install pear packages. This would be easy and I will
be relying on a stable well-tested pear cli, however reporting errors
properly would be tough as paraphrasing the output of pear may be tough.
Alternatively I can explore the steps that yum/apt-get/pear perform in
installation and then code them in java.
I think it would be great if we can reuse code that is well tested. The solution I think would work best is if the resolution phase (where the components are found and cspecs are generated) was pure java and then the actual materialization could be performed using existing cli's. Depends of course on how complex the cli's are versus how hard it would be to make them fit in with the overall build management process. But in general, I don't see a problem in invoking another language from within Buckminster.

Regards,
Thomas Hallgren


Back to the top