On 31-5-2012 5:00, Doug Barton wrote:
> On 05/30/2012 12:32, Mel Flynn wrote:
>> On 29-5-2012 19:06, Doug Barton wrote:
>>> On 5/29/2012 4:00 AM, Mel Flynn wrote:
On 29-5-2012 7:23, Doug Barton wrote:
>> Right. The issue I'm talking about is that fixing the problem of staying
>> with a versio
On 05/30/2012 12:48, Michael Scheidell wrote:
> Ditto on perl. UPDATING is wrong on steps. you can't upgrade perl, you
> need to delete it and everything it depends on and start from scratch.
For portmaster, you can do this which catches the majority of problems.
portmaster -o lang/perlNEWVER l
On 05/30/2012 12:32, Mel Flynn wrote:
> On 29-5-2012 19:06, Doug Barton wrote:
>> On 5/29/2012 4:00 AM, Mel Flynn wrote:
>>> On 29-5-2012 7:23, Doug Barton wrote:
>
>>> Not too hard for leaf ports. But with ports that are depended on, there
>>> is always a default, whether it's named that way or n
On 05/29/2012 12:08, Matthew D. Fuller wrote:
> On Tue, May 29, 2012 at 11:48:00AM -0700 I heard the voice of
> Doug Barton, and lo! it spake thus:
>> The whole concept of category/portname where there are multiple
>> versions of portname is flawed. The DEFAULT_PORTNAME_VER mechanism
>> works just
On 5/30/12 3:32 PM, Mel Flynn wrote:
Right. The issue I'm talking about is that fixing the problem of staying
with a version, introduces a problem for people that have their software
up-to-date and don't use deprecated features. Instead of simply
upgrading they now have to jump through hoops of
On 29-5-2012 19:06, Doug Barton wrote:
> On 5/29/2012 4:00 AM, Mel Flynn wrote:
>> On 29-5-2012 7:23, Doug Barton wrote:
>> Not too hard for leaf ports. But with ports that are depended on, there
>> is always a default, whether it's named that way or not. You're just
>> changing the problem slight
On Tue, May 29, 2012 at 11:48:00AM -0700 I heard the voice of
Doug Barton, and lo! it spake thus:
>
> With respect to those involved, the lang/python port is a special
> kind of problem.
I agree. IME, it causes more confusion than it solves. I don't ever
bother having lang/python on any systems
On 5/29/2012 11:25 AM, Olli Hauer wrote:
> On 2012-05-29 19:06, Doug Barton wrote:
>> On 5/29/2012 4:00 AM, Mel Flynn wrote:
>>> On 29-5-2012 7:23, Doug Barton wrote:
On 5/21/2012 9:40 AM, Miroslav Lachman wrote:
> I think that the best will be to not have any default "php5" port and
>
On 2012-05-29 19:06, Doug Barton wrote:
> On 5/29/2012 4:00 AM, Mel Flynn wrote:
>> On 29-5-2012 7:23, Doug Barton wrote:
>>> On 5/21/2012 9:40 AM, Miroslav Lachman wrote:
I think that the best will be to not have any default "php5" port and
just use php52, php53, php54, php5X, php60... a
On 5/29/2012 4:00 AM, Mel Flynn wrote:
> On 29-5-2012 7:23, Doug Barton wrote:
>> On 5/21/2012 9:40 AM, Miroslav Lachman wrote:
>>> I think that the best will be to not have any default "php5" port and
>>> just use php52, php53, php54, php5X, php60... as we have apache20,
>>> apache22, apache24, or
On 29-5-2012 7:23, Doug Barton wrote:
> On 5/21/2012 9:40 AM, Miroslav Lachman wrote:
>> I think that the best will be to not have any default "php5" port and
>> just use php52, php53, php54, php5X, php60... as we have apache20,
>> apache22, apache24, or mysql50-server, mysql51-server, mysql55-serv
Doug Barton wrote:
On 5/21/2012 9:40 AM, Miroslav Lachman wrote:
I think that the best will be to not have any default "php5" port and
just use php52, php53, php54, php5X, php60... as we have apache20,
apache22, apache24, or mysql50-server, mysql51-server, mysql55-server.
There is no default ap
On 5/21/2012 9:40 AM, Miroslav Lachman wrote:
> I think that the best will be to not have any default "php5" port and
> just use php52, php53, php54, php5X, php60... as we have apache20,
> apache22, apache24, or mysql50-server, mysql51-server, mysql55-server.
>
> There is no default apache2 or mys
On 21/05/2012 20:03, Etienne Robillard wrote:
On 05/21/2012 02:51 PM, George Kontostanos wrote:
On Mon, May 21, 2012 at 6:36 PM, Chris Rees wrote:
On May 21, 2012 4:17 PM, "George Kontostanos"
wrote:
Dear all,
I just wanted to understand why did php54 became the default php port.
Consider
On 05/21/2012 02:51 PM, George Kontostanos wrote:
On Mon, May 21, 2012 at 6:36 PM, Chris Rees wrote:
On May 21, 2012 4:17 PM, "George Kontostanos"
wrote:
Dear all,
I just wanted to understand why did php54 became the default php port.
Considering that the majority of my clients want to sti
On Mon, 2012-05-21 at 18:40 +0200, Miroslav Lachman wrote:
> I think that the best will be to not have any default "php5" port and
> just use php52, php53, php54, php5X, php60... as we have apache20,
> apache22, apache24, or mysql50-server, mysql51-server, mysql55-server.
+1
I really appreciate
On Mon, May 21, 2012 at 6:36 PM, Chris Rees wrote:
>
> On May 21, 2012 4:17 PM, "George Kontostanos"
> wrote:
>>
>> Dear all,
>>
>> I just wanted to understand why did php54 became the default php port.
>>
>> Considering that the majority of my clients want to stick with php53
>> with the susosin
On Mon, May 21, 2012 at 06:40:11PM +0200, Miroslav Lachman wrote:
> Jason Hellenthal wrote:
> >
> >
> > On Mon, May 21, 2012 at 11:38:50AM -0400, Michael Scheidell wrote:
> >>
> >>
> >> On 5/21/12 11:36 AM, Chris Rees wrote:
> >>> When would have been a better time?
> >>>
> >> after it was regres
Jason Hellenthal wrote:
On Mon, May 21, 2012 at 11:38:50AM -0400, Michael Scheidell wrote:
On 5/21/12 11:36 AM, Chris Rees wrote:
When would have been a better time?
after it was regression tested?
after the security posture (susosin patch) wasn't downgraded?
after a announcement in por
After a reasonable amount of time has passed so more applications properly
support it
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@fre
On Mon, May 21, 2012 at 11:38:50AM -0400, Michael Scheidell wrote:
>
>
> On 5/21/12 11:36 AM, Chris Rees wrote:
> > When would have been a better time?
> >
> after it was regression tested?
> after the security posture (susosin patch) wasn't downgraded?
after a announcement in ports/UPDATING s
On 5/21/12 11:36 AM, Chris Rees wrote:
When would have been a better time?
after it was regression tested?
after the security posture (susosin patch) wasn't downgraded?
--
Michael Scheidell, CTO
>*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheid
On May 21, 2012 4:17 PM, "George Kontostanos"
wrote:
>
> Dear all,
>
> I just wanted to understand why did php54 became the default php port.
>
> Considering that the majority of my clients want to stick with php53
> with the susosin patch, I can't blame them, it is really very annoying
> that we
On 5/21/12 11:17 AM, George Kontostanos wrote:
Because currently there is no other way to do it unless you delete all
your php5 packages and recompile them again under php53.
I think there was a published 'hack' to let you rename everything
php5->php53 in /var/db/pkg and /var/db/ports.
This
Dear all,
I just wanted to understand why did php54 became the default php port.
Considering that the majority of my clients want to stick with php53
with the susosin patch, I can't blame them, it is really very annoying
that we have to schedule a down time window so that we migrate from
php to p
On 15 May 2012 11:17, Michael Scheidell wrote:
> -1
> susosin patch is not a 'compatibility' issue. it is a security issue.
> I would consider recommending a lang/php54 port, for people who absolutely
> need it. include the 'WITH_SUHOSIN_PATCH' knob and mark it 'IGNORE' so that
> anyone who expe
On 5/15/12 11:05 AM, Svyatoslav Lempert wrote:
So I think we need release a new version without suhosin patch and
check the compatibility of all ports that depend on it (before), and
then when suhosin will appear (if there), then simply add it to the
port.
-1
susosin patch is not a 'compatibi
2012/5/15 Olivier Mueller :
>> >> FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
>> >> portstree. Thank you in advance.
>> >
>> > I'm just waiting for final release of suhosin (both patch and extension)
>> > to commit the update.
>>
>> Do you know the release date of suhosin for
Hi Svyatoslav,
On Sat, 2012-05-12 at 03:12 +0900, Svyatoslav Lempert wrote:
> 2012/4/19 Alex Dupre :
> >> FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
> >> portstree. Thank you in advance.
> >
> > I'm just waiting for final release of suhosin (both patch and extension)
> > to
On 5/11/12 2:12 PM, Svyatoslav Lempert wrote:
2012/4/19 Alex Dupre:
FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
portstree. Thank you in advance.
I'm just waiting for final release of suhosin (both patch and extension)
to commit the update.
Do you know the release date
2012/4/19 Alex Dupre :
>> FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
>> portstree. Thank you in advance.
>
> I'm just waiting for final release of suhosin (both patch and extension)
> to commit the update.
>
Do you know the release date of suhosin for this version? Stefan Es
Svyatoslav Lempert ha scritto:
> FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
> portstree. Thank you in advance.
I'm just waiting for final release of suhosin (both patch and extension)
to commit the update.
--
Alex Dupre
___
freeb
Hello, Alex!
FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
portstree. Thank you in advance.
I'm really waiting for this moment because I was going to install a
large number of new servers with the new version of PHP (version 5.4
should be so you do not have a problem with a maj
On 12.03.12 09:45, Alex Dupre wrote:
Mr Dandy wrote:
May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
current lang/php5 into lang/php53?
Probably current maintainer of php (@ale) has the plan ;)
released, then probably you should stick to lang/php52 port, or find a
m
> Anyway I think that the steps of launching a new port/port usage/port
> deprecation is necessary for this exact reason. The other way would be to
> freeze all the tree from time to time (i.e. several months) and ask projects
> maintainers/developers to stick to each freeze. FreeBSD system do t
Le 12 mars 2012 à 15:00, Miroslav Lachman a écrit :
> Jerry wrote:
>> On Mon, 12 Mar 2012 13:19:40 +0100
>> Miroslav Lachman articulated:
>>
>>> I really understand that you don't have a time or will to maintain
>>> more than 1 version of PHP - it is not an easy task. But what is the
>>> differe
Jerry wrote:
On Mon, 12 Mar 2012 13:19:40 +0100
Miroslav Lachman articulated:
I really understand that you don't have a time or will to maintain
more than 1 version of PHP - it is not an easy task. But what is the
difference between more versions of PHP in the ports tree and more
versions of Py
Le 12 mars 2012 à 09:45, Alex Dupre a écrit :
> Mr Dandy wrote:
>> May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
>> current lang/php5 into lang/php53?
>>
>> Probably current maintainer of php (@ale) has the plan ;)
>
> I've already created patches to update the curre
On Mon, 12 Mar 2012 13:19:40 +0100
Miroslav Lachman articulated:
> I really understand that you don't have a time or will to maintain
> more than 1 version of PHP - it is not an easy task. But what is the
> difference between more versions of PHP in the ports tree and more
> versions of Python,
Alex Dupre wrote:
Mr Dandy wrote:
May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
current lang/php5 into lang/php53?
Probably current maintainer of php (@ale) has the plan ;)
I've already created patches to update the current php5 port to 5.4. I'm
waiting for fixes to
Mr Dandy wrote:
> May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
> current lang/php5 into lang/php53?
>
> Probably current maintainer of php (@ale) has the plan ;)
I've already created patches to update the current php5 port to 5.4. I'm
waiting for fixes to other main p
Mr Dandy wrote:
On Sunday 11 March 2012 19:29:09 Svyatoslav Lempert wrote:
Hello,
please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933
May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
current lang/php5 into lang/php53?
It is to early to make it a default PHP p
2012/3/12 Mr Dandy :
>> please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933
>
> May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
> current lang/php5 into lang/php53?
>
No, I wrote about this a few weeks ago to ports@ - PHP 5.4 is not
compatible with PHP 5.3, depric
On Sunday 11 March 2012 19:29:09 Svyatoslav Lempert wrote:
> Hello,
> please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933
May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
current lang/php5 into lang/php53?
Probably current maintainer of php (@ale) has the plan ;
Hello,
please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933
--
Svyatoslav
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org
Hi All,
PHP 5.4.0 was released today -
http://www.php.net/archive/2012.php#id2012-03-01-1
Any ideas on when it'll be in the ports collection? The latest version I
can see in ports is php5-5.3.10_1
Regards
___
freebsd-ports@freebsd.org ma
46 matches
Mail list logo
