Andriy Gapon writes:
It seems that it is a kind of bloating to require python with X (even if only
a
small portion of it is needed). Unfortunately upstream guys maintain
xcb-proto and
xcbgen in the same distribution. But a trend among packgers seem to be to
split
these two into separate
On Fri, 08 May 2009 12:36:58 +0530 Ashish SHUKLA wrote:
Andriy Gapon writes:
It seems that it is a kind of bloating to require python with X (even if
only a
small portion of it is needed). Unfortunately upstream guys maintain
xcb-proto and
xcbgen in the same distribution. But a trend
on 08/05/2009 10:06 Ashish SHUKLA said the following:
Andriy Gapon writes:
It seems that it is a kind of bloating to require python with X (even if
only a
small portion of it is needed). Unfortunately upstream guys maintain
xcb-proto and
xcbgen in the same distribution. But a trend among
Hello Alexander!
Tue, May 05, 2009 at 04:28:20PM +0400 you wrote:
Hi all!
I am also interested in it. I have lots of questions about valgrind:
1) Is it working at all? I always receive SIGBUS on 7x.
2) Is our valgrind from http://valgrind.org/ or valgrind.kde.org?
3) valgrind.org lists
Hello dear developers!!!
please update transmission port to version 1.60
--
best regards
Sergienko Stanislav
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Andriy Gapon writes:
on 08/05/2009 10:06 Ashish SHUKLA said the following:
Andriy Gapon writes:
It seems that it is a kind of bloating to require python with X (even if
only a
small portion of it is needed). Unfortunately upstream guys maintain
xcb-proto and
xcbgen in the same
On Fri, 08 May 2009 17:05:55 +0530 Ashish SHUKLA wrote:
IMHO,
FreeBSD is not a package based system primarily. It is ports based and
in ports based system you've the freedom to specify the OPTIONS with
which you want port to be installed and a package to be built for it.
Please don't
on 08/05/2009 14:35 Ashish SHUKLA said the following:
Well no ideas about netbsd's pkgsrc system, but debian is a package
based system. Being a package based system, you've to create a separate
package for each combination of options you're going to support. IMHO,
FreeBSD is not a package
I submitted a PR over a month ago requesting a change to the net-snmp
port. There are several options in the port which currently require
compile-time defines to enable or disable. The PR contained a patch to
simply make these available via the ports configuration system (make
config).
On Fri, 2009-05-08 at 16:17 +0300, Andriy Gapon wrote:
on 08/05/2009 14:35 Ashish SHUKLA said the following:
Well no ideas about netbsd's pkgsrc system, but debian is a package
based system. Being a package based system, you've to create a separate
package for each combination of options
It has recently come to my attention that some commiters obfuscate
email addresses in the CVS logs, e.g:
Submitted by: Dominic Fandrey kamikaze AT bsdforen.de (maintainer)
Is this a policy? I prefer for my email address not to be obfuscated:
Submitted by: Dominic Fandrey kamik...@bsdforen.de
on 08/05/2009 18:06 Robert Noland said the following:
I think that a slave port is ok in this case. As long as dependencies
can be cleanly tracked and it doesn't produce conflicts. Meaning that
the user shouldn't have to select one port over the other.
Right. One port should complement the
2009/5/8 Sergey Zaharchenko doublef-...@yandex.ru:
Hardly an alternative, but devel/leaktracer might be of some help.
That's what I use. This is C++ only.
I've tried it. Using is like a breathe. And does it's job.
Thank you.
Alexander Churanov
___
2009/5/8 Xin LI delp...@delphij.net:
That's Revision 352 and not 3.52 nor 3.5.2...
Ah, it's clear now.
As far as I am aware Peter Wemm worked on a valgrind port which is
available on p4. Haven't give it a twist yet as it seems that we need
more work for amd64...
Is it checked into the
Dominic Fandrey wrote:
It has recently come to my attention that some commiters obfuscate
email addresses in the CVS logs, e.g:
Submitted by: Dominic Fandrey kamikaze AT bsdforen.de (maintainer)
Is this a policy? I prefer for my email address not to be obfuscated:
Submitted by: Dominic Fandrey
* Josh Rickmar (joshua_rick...@eumx.net) wrote:
starup-notification was updated, and I've just committed update of
awesome to 3.3-rc2. This should have no problems with new xcb-util.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber:
On Fri, 8 May 2009, Dmitry Marakasov wrote:
* Josh Rickmar (joshua_rick...@eumx.net) wrote:
starup-notification was updated, and I've just committed update of
awesome to 3.3-rc2. This should have no problems with new xcb-util.
Thanks!
Yeah, I saw the update to 3.3-rc2 and the new
Hi Alexander,
do you plan to implement MAKE_JOBS_SAFE for bsd.scons.mk as well?
I wonder if just adding _MAKE_JOBS to SCONS_ENV would be enough since -j
is also supported for scons.
--
Oliver Lehmann
http://www.pofo.de/
http://wishlist.ans-netz.de/
Re: BSDCan Ports BOF: http://wiki.freebsd.org/IvanVoras/PkgTransProposal
It's there... if anyone's still interested, please contact me.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe,
Hi Alexander,
do you plan to implement MAKE_JOBS_SAFE for bsd.scons.mk as well?
I wonder if just adding _MAKE_JOBS to SCONS_ENV would be enough since -j
is also supported for scons.
That should be enough. scons supports -j.
Alex
___
I am the octave-forge maintainer.
The octave forge source files have been updated. Quite a few of the new
source packages require octave-devel (3.1.55) instead of octave itself.
I am not quite sure what to do. I was hoping some end users could
give me their opinion. Here are some options:
From: Stephen Montgomery-Smith step...@missouri.edu
Subject: octave forge update issues
Date: Fri, 08 May 2009 17:40:18 -0500
I am the octave-forge maintainer.
The octave forge source files have been updated. Quite a few of the
new source packages require octave-devel (3.1.55) instead of
INDEX build failed with errors:
Generating INDEX-6 - please wait..pkg_info: not found
pkg_info: not found
pkg_info: not found
pkg_info: not found
Makefile, line 15: Could not find
/a/erwin/tindex/ports/x11/gambas2-gb-desktop/../../lang/gambas2-base/Makefile
make: fatal errors encountered --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Polyack wrote:
I submitted a PR over a month ago requesting a change to the net-snmp
port. There are several options in the port which currently require
compile-time defines to enable or disable. The PR contained a patch to
simply make
Greg Larkin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Steve,
I'll take this PR and commit it. I added to your patch to include the
other WITH_* variables in OPTIONS and generally changed
!defined(WITHOUT_FOO) tests to defined(WITH_FOO). Also, the patch
doesn't require a
INDEX build failed with errors:
Generating INDEX-6 - please wait..pkg_info: not found
pkg_info: not found
pkg_info: not found
pkg_info: not found
Done.
make_index: gambas2-2.12: no entry for /usr/ports/editors/gambas2-ide
Committers on the hook:
acm bsam dhn garga kwm marius nork nox pgj
26 matches
Mail list logo
