From owner-freebsd-ports@FreeBSD.ORG  Wed Aug 13 16:43:24 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 88663B46
 for <ports@freebsd.org>; Wed, 13 Aug 2014 16:43:24 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3B7B52EED
 for <ports@freebsd.org>; Wed, 13 Aug 2014 16:43:24 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1XHbdw-000Ftb-TU; Wed, 13 Aug 2014 18:43:20 +0200
Date: Wed, 13 Aug 2014 18:43:20 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Dennis Glatting <freebsd@pki2.com>
Subject: Re: FreeBSD unmaintained ports which are currently scheduled for
 deletion
Message-ID: <20140813164320.GK9400@home.opsec.eu>
References: <20140807153648.GO2644@home.opsec.eu>
 <1407811941.3895.236.camel@btw.pki2.com>
 <20140812045801.GC9400@home.opsec.eu>
 <1407863151.3895.237.camel@btw.pki2.com>
 <20140812193436.GE9400@home.opsec.eu>
 <1407891372.3895.266.camel@btw.pki2.com>
 <20140813041709.GF9400@home.opsec.eu>
 <1407904268.3895.270.camel@btw.pki2.com>
 <20140813044253.GA67425@over-yonder.net>
 <1407947824.3895.274.camel@btw.pki2.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1407947824.3895.274.camel@btw.pki2.com>
Cc: ports@freebsd.org, "Matthew D. Fuller" <fullermd@over-yonder.net>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Aug 2014 16:43:24 -0000

Hi!

> On Tue, 2014-08-12 at 23:42 -0500, Matthew D. Fuller wrote:
> > On Tue, Aug 12, 2014 at 09:31:08PM -0700 I heard the voice of
> > Dennis Glatting, and lo! it spake thus:
> > > 
> > > do_install in the Makefile does the chown.
> > 
> > Generally you'd want to do something more like using @owner/@group in
> > plist, rather than chown'ing in the stage.  Doing that would break
> > building as non-root, too.
> 
> What's the order? plist cannot change owner/group unless it is defined.
> Or, does plist execution happen /after/ the make process creates the
> owner/group entries?

If you some file bin/myfile1 in the pkg-plist which need to be owned by some
user etc, then:

[...]
bin/myfile0
@owner www
@group www
bin/myfile1
@owner root
@group wheel
bin/myfile2
[...]

should probably work. Can you try it ?

-- 
pi@opsec.eu            +49 171 3101372                         6 years to go !