Hi,
does someone has started updating the linux-js port for the new USB
interface in the kernel? I'm trying it at the moment and do not want to do
work twice.
Greetings,
Martin L.
PS: I'm not subscribed to the ports mailing list - so please also reply
directly.
Hey everyone,
Does anyone know of there is someone working on updating the input-wacom
driver ? The current port is broken on FreeBSD = 8 and outdated. It
would be a shame if the driver realy dies; without the absolute
positioning the pen-tablets are not as usefull as they could be. I'm
=== Building for ghostscript8-8.70
/bin/mkdir -p /usr/ports/print/ghostscript8/work/ghostscript-8.70/obj
/bin/mkdir -p /usr/ports/print/ghostscript8/work/ghostscript-8.70/bin
/bin/mkdir -p
/usr/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include
/bin/ln -s -f
On Sun, 20 Dec 2009 12:38:05 +0100
Frank Staals fr...@fstaals.net articulated:
Hey everyone,
Does anyone know of there is someone working on updating the
input-wacom driver ? The current port is broken on FreeBSD = 8 and
outdated. It would be a shame if the driver realy dies; without the
This was under stable/6; it may be relevant to note that as I have 4
slices configured on my laptop's disk, each of which is bootable
(stable/6, stable/7, stable/8, head), /usr/ports is actually a symlink
from each of those slices to a file system that is mountable regardless
of which slice is
On Sun, 20 Dec 2009 12:39:48 +0100
Martin Laabs i...@martinlaabs.de articulated:
Hi,
does someone has started updating the linux-js port for the new USB
interface in the kernel? I'm trying it at the moment and do not want
to do work twice.
Greetings,
Martin L.
PS: I'm not
On Sun, Dec 20, 2009 at 05:18:40AM -0800, David Wolfskill wrote:
This was under stable/6; it may be relevant to note that as I have 4
slices configured on my laptop's disk, each of which is bootable
(stable/6, stable/7, stable/8, head), /usr/ports is actually a symlink
from each of those
On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
...
(Though I note that
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
does seem to be populated with several other files.)
is this i386?
Aye
I reported this already for sparc and ia64:
Frank Staals wrote:
Hey everyone,
Does anyone know of there is someone working on updating the input-wacom
driver ? The current port is broken on FreeBSD = 8 and outdated. It
would be a shame if the driver realy dies; without the absolute
positioning the pen-tablets are not as usefull as
On Sun, 20 Dec 2009 05:32:38 -0800
David Wolfskill da...@catwhisker.org wrote:
On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
...
(Though I note that
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
does seem to be populated with several other files.)
Dominic Fandrey wrote:
Frank Staals wrote:
Hey everyone,
Does anyone know of there is someone working on updating the input-wacom
driver ? The current port is broken on FreeBSD = 8 and outdated. It
would be a shame if the driver realy dies; without the absolute
positioning the pen-tablets
On 20.12.2009 14:18 (UTC+1), David Wolfskill wrote:
This was under stable/6; it may be relevant to note that as I have 4
slices configured on my laptop's disk, each of which is bootable
(stable/6, stable/7, stable/8, head), /usr/ports is actually a symlink
from each of those slices to a file
Hi everyone!
On Sat, 5 Dec 2009 10:42:43 +0900
Norikatsu Shigemura n...@freebsd.org wrote:
I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri,
graphics/libGL*, graphics/libglut, graphics/mesa-demos and
graphics/libdrm. Please see also my attached patch file.
On Sun, Dec 20, 2009 at 08:25:08AM -0500, Jerry wrote:
OK, jylef...@freebsd.org is listed in the 'pkg-descr' file, although
apparently he no longer maintains the port. You might try contacting
them anyway.
Jean-Yves has not been active for over 2 years now.
(This is kind of why I don't like
Hi list,
per suggestion of the original poster, I added a desktop entry to the
Makefile of devel/argouml. Installing the port fails because the
resulting pkg-plist is incorrect. The patch seems correct according to
the Porters Handbook (
David Wolfskill da...@catwhisker.org wrote
in 20091220133238.gr...@bunrab.catwhisker.org:
da On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
da ...
da (Though I note that
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
da does seem to be populated with
On Sun, 20 Dec 2009 10:14:19 -0600
Mark Linimon lini...@lonesome.com articulated:
On Sun, Dec 20, 2009 at 08:25:08AM -0500, Jerry wrote:
OK, jylef...@freebsd.org is listed in the 'pkg-descr' file, although
apparently he no longer maintains the port. You might try contacting
them anyway.
Doug Barton wrote:
Miroslav Lachman wrote:
I don't know if it is well known / documented somewhere in portmaster,
but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long
options
This is why all of the ports tools should be in the ports tree. :)
I just added the fix to the svn
On Mon, 21 Dec 2009 00:34:22 +0900
Norikatsu Shigemura n...@ninth-nine.com wrote:
I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri,
graphics/libGL*, graphics/libglut, graphics/mesa-demos and
graphics/libdrm. Please see also my attached patch file. I'll
On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
David Wolfskill da...@catwhisker.org wrote
in 20091220133238.gr...@bunrab.catwhisker.org:
da On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
da ...
da (Though I note that
Miroslav Lachman wrote:
It is not working - pkg_add on 6.3 has no option for Install the
package without fetching and installing dependencies. I mean, there is
no long nor short option for this, so this portmaster's functionality
cannot be easily ported to 6.3. That's why I suggest to disable
Mark Linimon wrote:
(This is kind of why I don't like the entries in pkg-descr; they
just become stale.)
Yes, especially if the person who resets MAINTAINER does not also
update the pkg-descr. :)
Doug
--
Improve the effectiveness of your Internet presence with
a domain name
Hi!
I did try to update port from the subject and I got:
Error: /undefinedfilename in --file--
Operand stack:
On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
Fixed just now. This build error occurred only when WITH_FT_BRIDGE
was enabled regardless of the platform.
I'm still not able to build this. I've updated my ports tree which
hasn't helped. Is there anything else I can do to get
On Mon, Dec 21, 2009 at 12:54:42AM +, Jamie Griffin wrote:
On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
Fixed just now. This build error occurred only when WITH_FT_BRIDGE
was enabled regardless of the platform.
I'm still not able to build this. I've updated my
On Mon, Dec 21, 2009 at 12:54:42AM +, Jamie Griffin wrote:
On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
Fixed just now. This build error occurred only when WITH_FT_BRIDGE
was enabled regardless of the platform.
I'm still not able to build this. I've updated my
Jamie Griffin j...@koderize.com wrote
in 20091221005442.ga54...@bsdbox.koderize.com:
jg On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
jg
jg Fixed just now. This build error occurred only when WITH_FT_BRIDGE
jg was enabled regardless of the platform.
jg
jg I'm still not able
On Mon, Dec 21, 2009 at 12:57:50AM +, Anton Shterenlikht wrote:
cd /usr/ports/print/ghostscript8
make distclean
make rmconfig
make
This did the trick. Oddly, though, I did do this about an hour ago and
it still failed but, and probably completely coincidental, I rebooted
and gave it
On Fri, Dec 18, 2009 at 01:40:58PM +, Anton Shterenlikht wrote:
On Fri, Dec 18, 2009 at 03:17:40PM +0300, Andrew Belashov wrote:
Hi, Anton!
Anton Shterenlikht wrote:
on FreeBSD 9.0-CURRENT sparc64
port devel/gobject-introspection fails to build:
Making all in gir
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users 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
build environments. The most common
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users 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
build environments. The most common
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
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
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as forbidden in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port,
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as forbidden in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port,
35 matches
Mail list logo
