Bradesco S/A
ID do Cliente:
BR0013581
Prezado Cliente,
Por motivos de segurana comunicamos a todos os clientes que, visando
barrar o co
On Tue, Mar 30, 2010 at 9:36 PM, Arseny Nasokin wrote:
> On 31 Mar 2010, at 04:14, Garrett Cooper wrote:
>
>> Today binary packages are rolled as generic as possible provided the
>> architecture they're built for and are monolithic, meaning that they
>> contain the build, lib, patch, and run depe
On Tue, Mar 30, 2010 at 10:19 PM, Doug Barton wrote:
> On 03/30/10 21:36, Arseny Nasokin wrote:
>> I don't clearly understand, will be ports system removed?
>
> At this time all discussion is theoretical. LONG before we make any
> actual changes the users will have a chance to chime in, and will b
I can now confirm that with Xin's patch for zlib that all the qt4 stuff
builds, I updated virtualbox, and that builds and runs just fine.
Thanks for the quick response.
Doug
--
... and that's just a little bit of history repeating.
-- Propellerheads
I
On 03/30/10 21:36, Arseny Nasokin wrote:
> I don't clearly understand, will be ports system removed?
At this time all discussion is theoretical. LONG before we make any
actual changes the users will have a chance to chime in, and will be
notified if any actual changes are made.
Doug
--
On 31 Mar 2010, at 04:14, Garrett Cooper wrote:
On Tue, Mar 30, 2010 at 1:54 PM, Arseny Nasokin
wrote:
On 31 Mar 2010, at 00:49, Garrett Cooper wrote:
On Tue, Mar 30, 2010 at 1:25 PM, Arseny Nasokin
wrote:
On 30 Mar 2010, at 23:14, Alexey Shuvaev
wrote:
On Tue, Mar 30, 2010 at 01:0
On Tue, Mar 30, 2010 at 1:54 PM, Arseny Nasokin wrote:
> On 31 Mar 2010, at 00:49, Garrett Cooper wrote:
>
>> On Tue, Mar 30, 2010 at 1:25 PM, Arseny Nasokin wrote:
>>>
>>> On 30 Mar 2010, at 23:14, Alexey Shuvaev
>>>
>>> wrote:
>>>
On Tue, Mar 30, 2010 at 01:05:39AM +0400, Eir Nym wrote:
On Wednesday 31 March 2010 06:32:33 Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2010/03/30 12:22, Doug Barton wrote:
> > Testing it again I see that I didn't go far enough up to find the real
> > error, sorry Dirk.
>
> > The actual problem seems to be with zlib.h. This
There is an opennms port at: http://www.geeklan.co.uk/files/opennms/
however, it is a little dated.
I have attached a version that works for opennms 1.6.10 (at least it
worked for me with make install, after I uploaded the java dependencies
in /usr/ports/distfiles )
Attached is a tar ball of ope
On 31 Mar 2010, at 00:49, Garrett Cooper wrote:
On Tue, Mar 30, 2010 at 1:25 PM, Arseny Nasokin
wrote:
--
With pleasure
On 30 Mar 2010, at 23:14, Alexey Shuvaev >
wrote:
On Tue, Mar 30, 2010 at 01:05:39AM +0400, Eir Nym wrote:
I work on creating system for system and ports autobuild
On Tue, Mar 30, 2010 at 1:25 PM, Arseny Nasokin wrote:
>
>
> --
> With pleasure
>
> On 30 Mar 2010, at 23:14, Alexey Shuvaev
> wrote:
>
>> On Tue, Mar 30, 2010 at 01:05:39AM +0400, Eir Nym wrote:
>>>
>>> I work on creating system for system and ports autobuilder with custom
>>> settings for my F
--
With pleasure
On 30 Mar 2010, at 23:14, Alexey Shuvaev > wrote:
On Tue, Mar 30, 2010 at 01:05:39AM +0400, Eir Nym wrote:
I work on creating system for system and ports autobuilder with
custom
settings for my FreeBSD machines. I know about many programs, which
do
same, but I don't li
I can't comment intelligently on whether or not the fix below is
"correct," but with it, qt4-qmake compiles. I'll move on to try
recompiling the rest of qt4.
Doug
On 03/30/10 12:32, Xin LI wrote:
> On 2010/03/30 12:22, Doug Barton wrote:
>> Testing it again I see that I didn't go far enough up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010/03/30 12:22, Doug Barton wrote:
> Testing it again I see that I didn't go far enough up to find the real
> error, sorry Dirk.
>
> The actual problem seems to be with zlib.h. This is from qt4-gui:
[...]
> -DQ_INTERNAL_QAPP_SRC -DQT_CORE_LIB -D_
Testing it again I see that I didn't go far enough up to find the real
error, sorry Dirk.
The actual problem seems to be with zlib.h. This is from qt4-gui:
c++ -c -pipe -g -g -g -I../../include/Qt -I../../include -D_REENTRANT
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -g
-fv
On Tue, Mar 30, 2010 at 01:05:39AM +0400, Eir Nym wrote:
> I work on creating system for system and ports autobuilder with custom
> settings for my FreeBSD machines. I know about many programs, which do
> same, but I don't like strange depends, which are not controlled by
> OPTIONS and some another
On Tue, 30 Mar 2010, Doug Barton wrote:
c++ -c -pipe -g -g -g -I../../include/Qt -I../../include -D_REENTRANT
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -g
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -W
-I/usr/local/include -I/usr/local/include/freetype2 -fPIC -DQT
Hallo Doug Barton,
I can not reproduce this.
The upstream code contains support for libpngi 1.4
#FreeBSD: ports/x11-toolkits/qt4-gui/Makefile,v 1.30 2010/03/28 06:47:25 dinoex
Exp $
kind regards Dirk
- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
- [dirk.me...@dinoex.sub.org],[dirk.me..
Hi folks,
* Updates which break shared libraries would not be allowed within such
> a branch/overlay (i.e. no updating gnome 2.xx to 2.x(x+1), libpng,
> libjpeg, xorg).
The easiest way to accomplish this is to replace FreeBSD with Ubuntu. I'm
not sure we really want this.
Personally, among ot
c++ -c -pipe -g -g -g -I../../include/Qt -I../../include -D_REENTRANT
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -g
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -W
-I/usr/local/include -I/usr/local/include/freetype2 -fPIC -DQT_SHARED
-DQT_BUILD_GUI_LIB -DQT_NO_USING_NA
On Tue 30 Mar 2010 at 04:55:01 PDT Matthias Andree wrote:
I don't think this proposal is useful. Technically it would work, but socially
it wouldn't. Why? RELENG_* tagging would require that port maintainers oversee
the implications for all supported FreeBSD releases, possibly run tinderboxen t
Am 30.03.2010 09:18, schrieb Garrett Cooper:
> There is one important note to make:
>
> Many times you're forced to upgrade packages because of ABI breakages,
> etc. What would happen if there was a CVE assigned for PNG tomorrow
> (like there was for JPEG a year and change ago) where mass changes
Am 30.03.2010 09:30, schrieb Garrett Cooper:
> If this is really slick and tinderbox / whatever tools is doing its
> job and no PRs have been reported for X number of days on a given port
> (would require tie-ins to GNATS, or whatever), perhaps it would be
> nice if ports were automatically `promo
On 30 March 2010 09:30, Garrett Cooper wrote:
> Sorry -- one last thing to kick around before I get off this topic:
>
> If this is really slick and tinderbox / whatever tools is doing its
> job and no PRs have been reported for X number of days on a given port
> (would require tie-ins to GNATS, o
Hi Matthias,
Just to clear things up a bit, pkg_install (which lives under
.../src/usr.sbin/pkg_install) is a suite of tools consisting of
pkg_{add,create,delete,info,version}.
On Mon, Mar 29, 2010 at 3:35 AM, Matthias Andree wrote:
> Garrett Cooper wrote on 2010-03-29:
>
[...]
>> It's real
On Tue, Mar 30, 2010 at 12:26 AM, Garrett Cooper wrote:
> On Tue, Mar 30, 2010 at 12:18 AM, Garrett Cooper wrote:
>> On Mon, Mar 29, 2010 at 11:35 AM, Ivan Voras wrote:
>>> Alexey Shuvaev wrote:
>>>
> One way to do it, my proposal, would be to maintain a stable "overlay"
> of the ports,
On Tue, Mar 30, 2010 at 12:18 AM, Garrett Cooper wrote:
> On Mon, Mar 29, 2010 at 11:35 AM, Ivan Voras wrote:
>> Alexey Shuvaev wrote:
>>
One way to do it, my proposal, would be to maintain a stable "overlay"
of the ports, one for each major supported branch (i.e. 6.x, 7.x, 8.x),
c
On Mon, Mar 29, 2010 at 12:49 PM, Ivan Voras wrote:
> Doug Hardie wrote:
>>
>> On 29 March 2010, at 08:57, Ivan Voras wrote:
>>
>>> In some cases the burdens are obvious - the maintainer(s) would need to
>>> e.g. maintain three versions of the ports - a random example would be
>>> e.g. X.Org 7.0 f
On Mon, Mar 29, 2010 at 11:35 AM, Ivan Voras wrote:
> Alexey Shuvaev wrote:
>
>>> One way to do it, my proposal, would be to maintain a stable "overlay"
>>> of the ports, one for each major supported branch (i.e. 6.x, 7.x, 8.x),
>>> containing ports deemed "important" for some reason.
>>>
>> What
On Mon, Mar 29, 2010 at 3:57 PM, eculp wrote:
> Quoting Ivan Voras :
>
>> Doug Hardie wrote:
>>>
>>> On 29 March 2010, at 08:57, Ivan Voras wrote:
>>>
In some cases the burdens are obvious - the maintainer(s) would need to
e.g. maintain three versions of the ports - a random example woul
30 matches
Mail list logo
