Brooks Davis wrote:
On Thu, Aug 10, 2006 at 03:25:38PM +0200, G?bor K?vesd?n wrote:
Brooks Davis wrote:
On Wed, Aug 09, 2006 at 05:59:18PM -0600, John E Hein wrote:
John E Hein wrote at 17:43 -0600 on Aug 9, 2006:
Well, the part that makes it annoying to duplicate i
Ade Lovett <[EMAIL PROTECTED]> writes:
> On Aug 09, 2006, at 12:36 , Stanislav Sedov wrote:
>> There is one important change in 2.60 - mandir and infodir
>> now point by default to ${prefix}/share/man and ${prefix}/share/info
>> accordingly, that differs slightly from FreeBSD mtree. So we need
>>
On 8/11/06, Kostik Belousov <[EMAIL PROTECTED]> wrote:
After recent upgrade of x264, I still cannot update vlc and
gstreamer-plugins-x26480:
gstreamer-plugins-x26480 build error:
if /bin/sh ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I.
-I. -I../.. -I/usr/X11R6/include -I/usr/l
Hi,
Anyone using the opera port successfully on -current?
--
- [EMAIL PROTECTED] http://www.db.net/~db
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]
Diane Bruce writes:
> Anyone using the opera port successfully on -current?
I use mozilla, but opera works; I have it open in front of me.
What's the problem?
Robert Huff
___
freebsd-ports@freebsd.org
> Please apply following patch to devel/linuxthreads:
While fixing compilation on recent RELENG_6, that patch is a minor regression
for those running older snapshots of FreeBSD 7.0-CURRENT.
Feel free to commit this patch or a modified version that doesn't include the
regression for older snapsho
IMHO trailing slashes are very good style:
1. It's easier to see that destination is a directory
2. In case the destination directory does not exist
a trailing slash will save you from a nasty bug
___
freebsd-ports@freebsd.org mailing list
http://lists.
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we are attempting to notify maintainers of
ports that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we are attempting to notify maintainers of
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exp
10 matches
Mail list logo
