From owner-freebsd-questions@FreeBSD.ORG Wed Jan 15 05:37:07 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 423A3926 for ; Wed, 15 Jan 2014 05:37:07 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 06F6E18ED for ; Wed, 15 Jan 2014 05:37:06 +0000 (UTC) Received: from r56.edvax.de (port-92-195-149-155.dynamic.qsc.de [92.195.149.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id B472D27609 for ; Wed, 15 Jan 2014 06:36:58 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s0F5aYQG002472 for ; Wed, 15 Jan 2014 06:36:34 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Wed, 15 Jan 2014 06:36:34 +0100 From: Polytropon To: FreeBSD Questions Subject: Combining pkg and "traditional ports" Message-Id: <20140115063634.d6d26d51.freebsd@edvax.de> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 05:37:07 -0000 With the upcoming OS standardization on pkg (pkgng) following the abolishment of the pkg_* toolset I'd like to ask questions to those who already actively use pkg and have probably encountered and solved the same "problems" that I'll be expecting: There are two cases where a binary package can't be used: a) There is no package. Not all ports have equivalent packages. For example, I've seen this recently for OpenArena. In this case, compiling is needed (and even switching to gcc instead of clang, OS v10-RC2). Another example is a localize OpenOffice / maybe LibreOffice. How is this handled when a pkg-based "upgrade all" is performed? b) The default options of the package can't be used. My favourite example is mplayer (including all imaginable codecs as well as mencoder and additionally the gmplayer and gmencoder X applications), but it could also apply for a HAL-less X and HAL-less applications. But also OpenOffice can be considered again, a localized version (german) with dependencies for KDE, Gnome and CUPS deactivated (because I don't use those). Can those be protected from being overwritten? Is there even a method of saying, like, "use binary packages to upgrade everything excepts ports 'foo', 'bar', 'meow' and 'moo', compile those, but make sure their dependencies are installed via packages when they are available and apply"? >From my experience so far, pkg works really great. I'd just like to know how it can be used in the few cases where the exceptions need to be made intendedly. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...