Re: Vim and Vim-lite ports broken options

On Sun, Jun 30, 2013 at 01:37:36AM +0200, Nikola Pavlović wrote: > Hello, > > Is it just me, or did the last revision[*] of editors/vim break options > for both it and editors/vim-lite? When I try to update vim-lite > optional dependencies from vim are forced on this port, so I get > mandatory Py

FreeBSD ports you maintain which are out of date

| 3.5.0 +-+ www/xpi-pentadactyl | 20130407| 20130630 +-+ If any of the above results are invalid, please check the

Re: Vim and Vim-lite ports broken options

(Please keep me CC'd as I'm not subscribed to -ports) Yup, it's all broken. I use vim-lite myself; the solution I found is to drop this into /etc/make.conf: .if ${.CURDIR:M*/editors/vim-lite} WITH_VIM_OPTIONS=yes .endif Then "cd /usr/ports/editors/vim-lite ; make config", make sure everything i

Problem building ports in a sandbox/jail using DESTDIR

Hi. I am trying to compile ports in a sandbox environment on FreeBSD-9.1-RELEASE using a snapshot of ports from 06/27/2013. I have a jail file system I setup using my own scripts that I am pointing $DESTDIR to. I am using 'zip' as the port for testing. The problem is, I get an error like this a

CFT: [patch] making -jX builds the default

Hi there, In attempt to catch (hopefully) last few remaining jobs-unsafe ports, and thus to make upcoming expruns fallouts easier to handle, I'm sending small patch I've been using locally for a while to get larger exposure. Patch was sent to portmgr@ guys for review about a month earlier, it see

Re: CFT: [patch] making -jX builds the default

On 06/30/13 16:40, Alexey Dokuchaev wrote: > Hi there, > > In attempt to catch (hopefully) last few remaining jobs-unsafe ports, and > thus to make upcoming expruns fallouts easier to handle, I'm sending small > patch I've been using locally for a while to get larger exposure. Patch > was sent to

Subversion 1.8 / FreeBSD 8 x86 STABLE Symlinks

When using svn 1.8 I have come across a situation where when it is used pointing to a symlink that refers to a working directory that a update will either segfault or exit prematurely and leave a lock held on the working directory that the symlink points to. This leaves you with one choice but

Re: Subversion 1.8 / FreeBSD 8 x86 STABLE Symlinks

On Sun, Jun 30, 2013 at 02:20:21PM -0400, Jason Hellenthal wrote: > When using svn 1.8 I have come across a situation where when it is used > pointing to a symlink that refers to a working directory that a update will > either segfault or exit prematurely and leave a lock held on the working > d

Re: Problem building ports in a sandbox/jail using DESTDIR

On Sun, Jun 30, 2013 at 11:29:53AM -0500, Vincent Stemen wrote: > Hi. I am trying to compile ports in a sandbox environment on > FreeBSD-9.1-RELEASE using a snapshot of ports from 06/27/2013. > > I have a jail file system I setup using my own scripts that I am pointing > $DESTDIR to. I am using

please take ports/179236

Would anyone mind taking ports/179236? ports/179236: Build failure (lib-depends) for net/tigervnc when HPJPG is enabled http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/179236 Thanks, -- `whois vmeta.jp | nkf -w` meta ___ freebsd-ports@freebsd.org m

Re: Vim and Vim-lite ports broken options

On Sun, Jun 30, 2013 at 01:37:36AM +0200, Nikola Pavlović wrote: > Hello, > > Is it just me, or did the last revision[*] of editors/vim break options > for both it and editors/vim-lite? When I try to update vim-lite > optional dependencies from vim are forced on this port, so I get > mandatory Py

update for print/cups-bjnp

Patch attached, confirmed to work on PCBSD 9.1. Sorry if you get two of these, but I'm not sure if the send-pr web interface works. -- Alfred Perlstein VP Software Engineering, iXsystems diff --git a/print/cups-bjnp/Makefile b/print/cups-bjnp/Makefile index ae80739..9c25c5a 100644 --- a/prin