Hi,
Currently, avahi conflicts with howl/mDNSResponder. As a user of KDE, I have
plenty of applications that depend on mDNSResponder. But at the same time, I am
a user of OpenOffice.org, Firefox, eclipse and many others that depend on avahi
(mainly because of gnome-vfs). The current conflict has
Arseny Nasokin wrote:
I had pressed ^C when portupgrade checks database. Portupgrade's db is locked
always after it.
I have tryed to remove db and lock, remove and install again portupgrade but
nothing happines.
What should I do in this case?
What portupgrade version do you use?
A
Hello,
When one builds (or attempts to build) a port, does the Makefile
know about dependencies and, if necessary, fetch and build any
that are needed but not found?
Thank you and kindest regards,
Charlie
PS It would be really helpful if each port/package at freebsd.org
had an indication
Hi!
I wonder what is the reason SDL has it's version appended everywhere
(include/SDL11 instead of include/SDL, libSDL-1.1.so instead of
libSDL.so, sdl11-config instead of sdl-config). It takes extra time when
porting SDL software, extra patches need to be added. Is there any good
reason for such
Charlie Sorsby wrote:
When one builds (or attempts to build) a port, does the Makefile
know about dependencies and, if necessary, fetch and build any
that are needed but not found?
Yes and yes.
[ ... ]
PS It would be really helpful if each port/package at freebsd.org
had an indication
On Jul 6, 2006, at 11:24 AM, Brooks Davis wrote:
Actually I think it's confused by the fact that the package name is
diablo-jdk and the version is freebsd6.i386.1.5.0.07.00. That's
just plain bogus.
So who is at fault? The ports infrastructure or the FreeBSD
foundation?
I don't know.
Charlie Sorsby writes:
When one builds (or attempts to build) a port, does the Makefile
know about dependencies and, if necessary, fetch and build any
that are needed but not found?
Yes.
PS It would be really helpful if each port/package at freebsd.org
had an indication
Freddie Cash wrote:
On Wed, July 5, 2006 2:08 pm, Chris Maness wrote:
Used to have this cool little tool on my slackware box to monitor
network traffic. Just curious as to why it has not been ported (are
there any issues with it?)
http://linux.maruhn.com/sec/netwatch.html
p.s. What would
On Thu, 2006-Jul-06 09:35:25 -0700, Chris Maness wrote:
Freddie Cash wrote:
Install trafshow instead.
This program seems to stay in memory after the shell closes and eats up
processor time. Top showed this thing at 98%. Does this app. have a bug?
Most likely. {p,k}trace it whilst it's eating
On Thu, 06 Jul 2006 12:07:55 -0400
Chuck Swiger [EMAIL PROTECTED] wrote:
Charlie Sorsby wrote:
When one builds (or attempts to build) a port, does the Makefile
know about dependencies and, if necessary, fetch and build any
that are needed but not found?
Yes and yes.
[ ... ]
PS It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 04 Jul 2006 07:43:08 +0200
Alexander Leidinger [EMAIL PROTECTED] wrote:
Quoting Alejandro Pulver [EMAIL PROTECTED] (from Sat, 1 Jul 2006
20:25:22 -0300):
But then how do the databases/dbXX ports achieve the same result
without it?
Hello all..
I have made a port of bonfire http://perso.orange.fr/bonfire/
and would like to publish it in the ports collection
After reading the ports documentation I
found nothing abou publishing it in the ports collection
Can someone, please, give me a direction on
how o publish the
On Thu, Jul 06, 2006 at 04:16:05PM -0300, Sergio Lenzi wrote:
Hello all..
I have made a port of bonfire http://perso.orange.fr/bonfire/
and would like to publish it in the ports collection
After reading the ports documentation I
found nothing abou publishing it in the ports
Freddie Cash wrote:
On Thu, July 6, 2006 9:35 am, Chris Maness wrote:
Freddie Cash wrote:
On Wed, July 5, 2006 2:08 pm, Chris Maness wrote:
Used to have this cool little tool on my slackware box to monitor
network traffic. Just curious as to why it has not been ported
On Thu, 06 Jul 2006 14:21:03 -0500, Lars Engels [EMAIL PROTECTED]
wrote:
On Thu, Jul 06, 2006 at 04:16:05PM -0300, Sergio Lenzi wrote:
Hello all..
I have made a port of bonfire http://perso.orange.fr/bonfire/
and would like to publish it in the ports collection
After reading the ports
On 7/6/06, michael johnson [EMAIL PROTECTED] wrote:
On 7/6/06, Jeremy Messenger [EMAIL PROTECTED] wrote:
On Thu, 06 Jul 2006 14:21:03 -0500, Lars Engels [EMAIL PROTECTED]
wrote:
On Thu, Jul 06, 2006 at 04:16:05PM -0300, Sergio Lenzi wrote:
Hello all..
I have made a port of bonfire
On Thu, 06 Jul 2006 14:35:11 -0500, michael johnson [EMAIL PROTECTED] wrote:
On 7/6/06, michael johnson [EMAIL PROTECTED] wrote:
On 7/6/06, Jeremy Messenger [EMAIL PROTECTED] wrote:
On Thu, 06 Jul 2006 14:21:03 -0500, Lars Engels [EMAIL PROTECTED]
wrote:
On Thu, Jul 06, 2006 at
On 7/6/06, Jeremy Messenger [EMAIL PROTECTED] wrote:
On Thu, 06 Jul 2006 14:35:11 -0500, michael johnson [EMAIL PROTECTED] wrote:
On 7/6/06, michael johnson [EMAIL PROTECTED] wrote:
On 7/6/06, Jeremy Messenger [EMAIL PROTECTED] wrote:
On Thu, 06 Jul 2006 14:21:03 -0500, Lars Engels
On Thu, Jul 06, 2006 at 09:58:54PM +0300, Ion-Mihai IOnut Tetcu wrote:
Actually support for 4.x is gone already. We're only required to mark
the ports broken or incorporate patches from the users. Of curse, we
try to fix broken ports on 4-STABLE but that battle is going to be lost.
The latest
On Thu, 6 Jul 2006 16:38:23 -0500 Mark Linimon wrote:
Further note: there may be a recent checkin affecting the linux_base
ports which completely skews this result; I am investigating. However.
there are 206 legitimate build errors on i386-4 now; that doesn't include
any port already marked
On Tue, Jul 04, 2006 at 09:22:09PM -0500, Mark Linimon wrote:
BROKEN is intended to be set in individual ports.
With IGNORE, the build cluster will never attempt to build these
ports. Common cases for IGNORE are for the CONFLICTS logic; for
licensing/packaging reasons; and for the
On Fri, Jul 07, 2006 at 02:45:02AM +0400, Boris Samorodov wrote:
I noticed a few days ago that the first site at FEDORA_CORE_SITES
(limestone.uoregon.edu) is acting not reliable. Your logs says the
same (most distributions were taken from the next site --
mirrors.kernel.org). I'd rather delete
Mark Linimon wrote:
The burden of trying to keep everything working on 4 i386 branches, 3
amd64 branches, and 3 sparc64 branches is too high at this point, especially
with the degree of drift in such things as header files and base compiler
between -4 and -5. Of course, most of these things
23 matches
Mail list logo
