From owner-freebsd-ports@FreeBSD.ORG  Fri Jul 25 19:30:37 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-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 D67DE202
 for <freebsd-ports@freebsd.org>; Fri, 25 Jul 2014 19:30:37 +0000 (UTC)
Received: from sam.nabble.com (sam.nabble.com [216.139.236.26])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B901B24DA
 for <freebsd-ports@freebsd.org>; Fri, 25 Jul 2014 19:30:37 +0000 (UTC)
Received: from [192.168.236.26] (helo=sam.nabble.com)
 by sam.nabble.com with esmtp (Exim 4.72)
 (envelope-from <zaphod@berentweb.com>) id 1XAlCP-00089x-1Y
 for freebsd-ports@freebsd.org; Fri, 25 Jul 2014 12:30:37 -0700
Date: Fri, 25 Jul 2014 12:30:37 -0700 (PDT)
From: Beeblebrox <zaphod@berentweb.com>
To: freebsd-ports@freebsd.org
Message-ID: <1406316637042-5931780.post@n5.nabble.com>
In-Reply-To: <1406297591500-5931719.post@n5.nabble.com>
References: <1406297591500-5931719.post@n5.nabble.com>
Subject: Re: Merging several branches with ports tree
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18
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: Fri, 25 Jul 2014 19:30:37 -0000

Andrzej Tobola wrote:

> I do not understand exactly ...
> but from a few years  I am using unionfs to place my mods of ports
> tree over the original:
>
>   /ftp/pub/BSD/FreeBSD/GIT/ports    2,1T    1,6T    553G
> 74%    /usr/ports <above>:/usr/local/ports          2,2T    2,2T
> 18G    99%    /usr/ports
> 
>   % mount | grep ports
>   /ftp/pub/BSD/FreeBSD/GIT/ports on /usr/ports (nullfs, read-only)
>   <above>:/usr/local/ports on /usr/ports (unionfs, read-only)

That's an interesting approach and nice idea.
My aim is to have a separate category for the modded ports, because
a) They're mostly not in the tree anyway and,
b) I need a way to keep track of modded ports for update failure.

In case there are others who find my explanation a bit incomprehensible:
* I download each repo/tree (git/svn) into its own folder.
* I then want to overlay each tree into /usr/ports, starting with ports,
gnome3, linux-c6 and finally my-port-collection
* When I update base ports tree, and try to place the latest overlay into
/usr/ports, the "rsync -au" command results in a ports tree with unforseen
errors. I need to correct this.
* I prefer to have my ports collection under a separate category and I need
to correct the script that injects categories into /usr/ports/Makefile &
Mk/bsd.ports.mk. Sending the folder for sub-category is of course trivial
with rsync.

Thanks for the idea!



-----
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Merging-several-branches-with-ports-tree-tp5931719p5931780.html
Sent from the freebsd-ports mailing list archive at Nabble.com.