On Fri, Jun 24, 2005 at 11:24:01PM +0200, Toni Mueller wrote:
> > i.e. WRKDIR gets set by the directory you're in, not ${PORTSDIR}
>
> yes, but WRKDIR should not be PORTSDIR in any case - it's two levels
> down for most ports, and three on some.
>
> Eg, WRKDIR=${PORTSDIR} + "/" + "sysutils/nut"
Hi,
On Thu, 23.06.2005 at 12:23:42 -0700, Michael Coulter <[EMAIL PROTECTED]> wrote:
> # PORTSDIR=/symlink_to_usr_ports cd /usr/ports/sysutils/nut && make
> show=WRKDIR
> /usr/ports/sysutils/nut/w-nut-2.0.0
>
> i.e. WRKDIR gets set by the directory you're in, not ${PORTSDIR
On Thu, Jun 23, 2005 at 09:02:13PM +0200, Toni Mueller wrote:
> I'm not sure about what you mean here,
# PORTSDIR=/symlink_to_usr_ports cd /symlink_to_usr_ports/sysutils/nut && make
show=WRKDIR
/symlink_to_usr_ports/sysutils/nut/w-nut-2.0.0
# PORTSDIR=/symlink_to_usr_ports cd /usr/ports/sysutils
Hi Nicolay,
On Wed, 22.06.2005 at 08:03:25 +0200, Nikolay Sturm <[EMAIL PROTECTED]> wrote:
> * Toni Mueller [2005-06-21]:
> > native-fswrite: filename match "/usr/S/ports/distfiles" then permit
> > native-fswrite: filename match "/usr/ports/sysutils/nut/w-nut-2.0.0"
> > then permit
>
> T
Hi,
On Tue, 21.06.2005 at 14:06:12 -0700, Michael Coulter <[EMAIL PROTECTED]> wrote:
> Lines like this one are the culprit. It looks like you ran make extract
> from /usr/ports as opposed to /usr/S/ports. In the case where WRKOBJDIR
> is not set, WRKDIR uses ${.CURDIR} as it's base path. I'm not
Hi,
On Tue, 21.06.2005 at 14:06:12 -0700, Michael Coulter <[EMAIL PROTECTED]> wrote:
> > Btw, while I'm at it, this machine, despite being amd64, creates
> > ...ports/packages/i386/... instead of ...porets/packages/amd64/...
>
> This is because you told it to :)
ok, stupid me :-|
Best,
--Toni
* Toni Mueller [2005-06-21]:
> native-fswrite: filename match "/usr/S/ports/distfiles" then permit
> native-fswrite: filename match "/usr/ports/sysutils/nut/w-nut-2.0.0"
> then permit
This indeed is a very strange entry. Is /usr/ports a hardlink to
/usr/S/ports? Otherwise I don't see
On Tue, Jun 21, 2005 at 10:13:04PM +0200, Toni Mueller wrote:
> native-fswrite: filename match "/usr/ports/sysutils/nut/w-nut-2.0.0"
> then permit
Lines like this one are the culprit. It looks like you ran make extract
from /usr/ports as opposed to /usr/S/ports. In the case where WRKOBJDI
Hi,
On Sat, 18.06.2005 at 22:34:11 +0200, Nikolay Sturm <[EMAIL PROTECTED]> wrote:
> * Toni Mueller [2005-06-18]:
> > - Building the port breaks when using systrace at archive extraction
> > phase:
> Show me the port's systrace.policy file, please. I cannot reproduce your
> problem.
no problem
* Toni Mueller [2005-06-18]:
> - Building the port breaks when using systrace at archive extraction
> phase:
Show me the port's systrace.policy file, please. I cannot reproduce your
problem.
Nikolay
On Sat, Jun 18, 2005 at 05:36:30PM +0200, Toni Mueller wrote:
>
> Hello,
>
> since there is no maintainer listed in the nut Makefile, I'd like to
> ask the list:
>
> - I assume that nut currently has no maintainer?
MAINTAINER= Marc Balmer <[EMAIL PROTECTED]> in -current ;-)
--
Alexandre Anri
Hello,
since there is no maintainer listed in the nut Makefile, I'd like to
ask the list:
- I assume that nut currently has no maintainer?
- Building the port breaks when using systrace at archive extraction
phase:
===> Extracting for nut-2.0.0
systrace: deny user: root, prog: /bin/tar,
12 matches
Mail list logo