From owner-freebsd-questions@FreeBSD.ORG Tue Jun 24 13:55:09 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B9A29F0 for ; Tue, 24 Jun 2014 13:55:09 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B8092C50 for ; Tue, 24 Jun 2014 13:55:08 +0000 (UTC) Received: from becker.bs.l (e180009210.adsl.alicedsl.de [85.180.9.210]) by mrelayeu.kundenserver.de (node=mreue102) with ESMTP (Nemesis) id 0MVteq-1XAZ8c2Vjc-00X7WJ; Tue, 24 Jun 2014 15:55:06 +0200 Received: from bsch by becker.bs.l with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WzRBh-000Jtk-Pp for freebsd-questions@freebsd.org; Tue, 24 Jun 2014 15:55:05 +0200 Date: Tue, 24 Jun 2014 15:55:05 +0200 From: Bertram Scharpf To: freebsd-questions@freebsd.org Subject: How do I build my own package server? Message-ID: <20140624135505.GA75895@becker.bs.l> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: Bertram Scharpf X-Provags-ID: V02:K0:gk9Fb8+9hIe/7eNuGaj4BkMLIOgfHikPKEIMI3pGaDY LkUps0YEmPw9hP2ZSfXfG9HkUAqj2tUJ+/Ah3PpCE8g2aD2V7O w4OvJqp90ie97dRl9nCeKs5mR2RiFl6MRqDfup9YwXrkWYYkxi uRLmsrvpjvS1rHfjgd4YWjyiddXB60EzcmqLB4GuxjIMKXsYbV 4AzhTs3J0uZRNU9lLTp61xmV9i4lt/2xO+Z9dIMCQGEt0SuEvZ Ug9l/esoDIJBXs4wkD1oujhq2WLhtJBiqeG2Wy/cU9tSFN1Hqn aBfS5pIJAYh0TncBIrbAo7H/YsIusol2Xdj1OHX+kR3ZPgRMs1 C6iaGijy6QO70k/9ZnXjMs72b9Dh8lx7u3s+pxv31 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 13:55:09 -0000 Hi, this is sort of what I did until now: Inside a jail: - SVN-Update "/usr/ports". - Merge my own patch files for several packages. - Find the outdated ports using a self-written tool. - Do "make clean" and "make package" for them. - Build a package list. On all other machines and jails: - Load the package list. - Find the outdated packages. - Do "pkg_delete" and "pkg_add" for them. Now, the pkg_* tools are no longer supported! Rewriting my update tools would take at least two days and I have better things to do. On the other side, I doubt whether it would go any faster learning some portmaster or portupgrade tool until I find the features I need. (Actually, I tried portmaster and soon was tired of seeing it redundantly cleaning and recompiling ports.) Therefore my question: Is there any documentation how to build a package server that can be understood in finite time? On the other side: I do not feel very well having loads of SQLite databases in the base system. Could it be worth the effort to further develop the traditional pkg_* tools? Thanks in advance, Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de