On Fri, Jul 17, 2009 at 6:24 PM, Greg Beaver wrote:
> Matteo Beccati wrote:
> > Lukas Kahwe Smith wrote:
> > > On 17.07.2009, at 03:04, Johannes Schlüter wrote:
> > > > On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
> > > > > I'd like to consider instead using svn:externals to pull in PEAR s
On 18.07.2009, at 01:01, Matteo Beccati wrote:
Greg Beaver ha scritto:
Matteo Beccati wrote:
Not really: it will copy the link, not its content. At least that
was my
experience when I managing releases for an internal project using
externals. What I usually did was to change the externals p
Greg Beaver ha scritto:
> Matteo Beccati wrote:
>> Not really: it will copy the link, not its content. At least that was my
>> experience when I managing releases for an internal project using
>> externals. What I usually did was to change the externals property to
>> point to a specific revision,
Matteo Beccati wrote:
> Lukas Kahwe Smith wrote:
>
>> On 17.07.2009, at 03:04, Johannes Schlüter wrote:
>>
>>
>>> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>>>
I'd like to consider instead using svn:externals to pull in PEAR stuff
directly from a STABLE branch f
Lukas Kahwe Smith wrote:
>
> On 17.07.2009, at 03:04, Johannes Schlüter wrote:
>
>> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>>> I'd like to consider instead using svn:externals to pull in PEAR stuff
>>> directly from a STABLE branch from somewhere in the pear/ hierarchy.
>>> This wo
On 17.07.2009, at 03:04, Johannes Schlüter wrote:
On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
I'd like to consider instead using svn:externals to pull in PEAR
stuff
directly from a STABLE branch from somewhere in the pear/ hierarchy.
This would allow us over at PEAR to push the ins
Johannes Schlüter wrote:
> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>
>> I'd like to consider instead using svn:externals to pull in PEAR stuff
>> directly from a STABLE branch from somewhere in the pear/ hierarchy.
>> This would allow us over at PEAR to push the installation phars
On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
> I'd like to consider instead using svn:externals to pull in PEAR stuff
> directly from a STABLE branch from somewhere in the pear/ hierarchy.
> This would allow us over at PEAR to push the installation phars into
> that branch at the same tim
On Fri, Jul 17, 2009 at 2:23 AM, Greg Beaver wrote:
>> Is it possible to have one single phar for all platforms? That would
>> already make the whole thing easier to manage.
>>
> This would be more challenging to do, but may be possible. The biggest
> problem is that go-pear is interactive, and i
Pierre Joye wrote:
> hi,
>
> On Fri, Jul 17, 2009 at 1:20 AM, Greg Beaver wrote:
>
>> Hi,
>>
>> I'd like to start a discussion on php-src/pear and how we can manage it
>> better for PHP 5.3, and to discuss the future of PEAR in PHP.
>>
>> First, take note that both internals@ and pear-dev@ are c
hi,
On Fri, Jul 17, 2009 at 1:20 AM, Greg Beaver wrote:
> Hi,
>
> I'd like to start a discussion on php-src/pear and how we can manage it
> better for PHP 5.3, and to discuss the future of PEAR in PHP.
>
> First, take note that both internals@ and pear-dev@ are copied on this
> email.
>
> For some
Hi,
I'd like to start a discussion on php-src/pear and how we can manage it
better for PHP 5.3, and to discuss the future of PEAR in PHP.
First, take note that both internals@ and pear-dev@ are copied on this
email.
For some background, currently the pear components are dynamically added
to a ch
12 matches
Mail list logo
