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 probl
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 probl
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
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, inclu
On 19.10.2012 23:19, Matthew Seaman wrote:
> skipped .
> https://github.com/pkgng/pkgng/commit/8e4cc67cffe8f0afd5c0e25651bd367e12196bbd
BIG thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
> No -- you only ever need to run pkg2ng once.
> /usr/bin/pkg will invoke /usr/local/bin/pkg automatically if
> /usr/local/bin/pkg is installed -- /usr/bin/pkg is a shim that exists to
> facilitate the installation of the actual /usr/local/bin/pkg binary.
> That's all normal.
> Now, the real prob
On Sun, 21 Oct 2012 08:30:05 +
freebsd-ports-requ...@freebsd.org wrote:
> FreeBSD unmaintained ports which are currently scheduled for
> deletion
> portname: games/fretsonfire
> broken because: does not build
> build errors: none.
> overview:
> http://port
On 21/10/2012 10:57, Thomas Mueller wrote:
> Actually, I find pkg in sbin directory as opposed to bin:
> /usr/sbin/pkg and /usr/local/sbin/pkg .
You're quire right. pkg lives in .../sbin. Sorry about that.
> I followed your steps 1 to 4, found 638 packages, found the correct
> permissions, and
"wait_on" does not scan for changes in sub-directories. Could a new switch
be added have it scan for changes in sub-directories?
Currently I am unable to make wait_on accept a variable as an input which
contains quotes (single or double) without an error.
Thank You
___
Hello,
Can someone help me to create the ports of pyspatialite
pypi.python.org/pypi/pyspatialite/3.0.1 ?
I managed to create the makefile to download the source but my knowledge
of python does not allow me to make the port correctly.
This binding is need by some extensions in Qgis and maybe other
On 10/19/12 11:25 AM, Thomas Abthorpe wrote:
> Pav Lucistnik, aka pav@, recently stepped down from his roll on the FreeBSD
> Ports Management team.
>
> Pav started on portmgr back in November 2006, he was the one responsible
> for many of the -exp runs over the years. His most dubious claim to fam
> On 21/10/2012 10:57, Thomas Mueller wrote:
> > Actually, I find pkg in sbin directory as opposed to bin:
> > /usr/sbin/pkg and /usr/local/sbin/pkg .
> You're quire right. pkg lives in .../sbin. Sorry about that.
> > I followed your steps 1 to 4, found 638 packages, found the correct
> > permi
On 21/10/2012 22:44, Thomas Mueller wrote:
> Now the problem is x11-toolkits/open-motif and lang/tcl85 allegedly trying
> to install files to the same location, meaning a conflict, and that has me
> stopped, Error 70. Is there any command under pkg that would help?
That's a problem with the unde
--- configure.orig 2012-10-21 21:46:34.996150862 -0700
+++ configure 2012-10-21 21:40:23.478149927 -0700
@@ -5800,7 +5800,7 @@
MAKEVER="freebsd"
LDFLAGS="-lpmc"
# HWPMC driver is available for FreeBSD >= 6
-FREEBSD_VERSION=`uname -r | cut -c 1`
+FREEBSD_VERSION=`uname
> On 21/10/2012 22:44, Thomas Mueller wrote:
> > Now the problem is x11-toolkits/open-motif and lang/tcl85 allegedly trying
> > to install files to the same location, meaning a conflict, and that has me
> > stopped, Error 70. Is there any command under pkg that would help?
> That's a problem with
On 22/10/2012 06:47, Thomas Mueller wrote:
> I looked in "man sysexits" and in the referenced file,
> /usr/include/sysexits.h : showed error codes 64 to 78.
>
> Where do I find documentation for other error codes?
If it's not described in the program's man page, then I'm afraid you'll
probably ha
16 matches
Mail list logo