From owner-freebsd-ports@FreeBSD.ORG Tue Aug 21 15:26:37 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A1821065672; Tue, 21 Aug 2012 15:26:37 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id B1FF58FC17; Tue, 21 Aug 2012 15:26:36 +0000 (UTC) Received: by vbmv11 with SMTP id v11so8692049vbm.13 for ; Tue, 21 Aug 2012 08:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mBg7v0UDBuXDhjwIzKsAbOC2Azz7QR+T+Tc/A6Bdji8=; b=Lhi5LIecXs4IaPXYwC4iSjZbO0ynLsN40G3QMSIwDXECimDi+qVhz08J1wOLvGlAAr cOa4h52gGnSwbV1MaXoGQx3o5qkKzO5uYetzFtbZx+dpi9IHL5tZ0Wbc87cjwdtRgfV0 NzfMyloiB/MP7TAH01A7rbbZl87mQFu4aFzgYXfp6VBKVnSqDj7Upw2kW1jx5O7O642O DL1NbCEA+rHXQ+6YikA8zTeqQaZJ2HzdM6eguTptW895VMtsh6ud+WNhoe+SJuJArV/q wKfU1mGJCjqpxeAzPQ36I36SwtOrMrbK4kC2+CX+w6odvpXdFkKmAaaZszyH0YDp7p86 Y1pA== MIME-Version: 1.0 Received: by 10.58.4.232 with SMTP id n8mr14750170ven.54.1345562795854; Tue, 21 Aug 2012 08:26:35 -0700 (PDT) Received: by 10.58.230.134 with HTTP; Tue, 21 Aug 2012 08:26:35 -0700 (PDT) In-Reply-To: <50339F1F.3040802@freebsd.org> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120820232147.GD23607@ithaqua.etoilebsd.net> <5033253D.4060807@FreeBSD.org> <20120821070436.GE23607@ithaqua.etoilebsd.net> <50339F1F.3040802@freebsd.org> Date: Tue, 21 Aug 2012 18:26:35 +0300 Message-ID: From: Kimmo Paasiala To: Lawrence Stewart Content-Type: text/plain; charset=UTF-8 Cc: freebsd-ports@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 15:26:37 -0000 On Tue, Aug 21, 2012 at 5:45 PM, Lawrence Stewart wrote: > On 08/21/12 17:04, Baptiste Daroussin wrote: >> On Tue, Aug 21, 2012 at 07:05:49AM +0100, Matthew Seaman wrote: >>> On 21/08/2012 00:21, Baptiste Daroussin wrote: >>>> On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote: >>>>> Baptiste Daroussin wrote: >>>>>> Please [...] ask question about pkgng [...] >>>>> >>>>> What would be the best practice of mixing ports with packages? >>>>> >>>>> The use case I have in mind is compiling Xorg ports locally >>>>> WITH_NEW_XORG and WITH_KMS, and using packages from >>>>> pkgbeta.freebsd.org for everything else. Is there some mixture of pkg >>>>> and portmaster flags that allows this kind of setup? >>>>> _______________________________________________ >>>>> freebsd-ports@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >>>>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >>>> >>>> There is no best practice for that unfortunatly, (as actually) the best for you >>>> is maybe to build your own pkgng repostories? >>>> http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example? >>>> >>>> We are open to suggestion here :) >>> >>> At the moment, it is about as tricky as mixing locally compiled ports >>> with pkg_tools packages: ie. it might work, or it might leave you a >>> quivering, sobbing mess lost in a pit of dark despair. >>> >>> One thing that should help is a proposal to record metadata like the SVN >>> revision number of the ports tree used to build repository packages into >>> the repository catalogue (repo.sqlite), so users can in principle check >>> out the same revision locally to build their own ports. Unfortunately >>> no one has written that yet, and its probably too late for it to make it >>> into release-1.0. >>> >> >> yes but it should definitly find its way to 1.1! > > > Agreed, though ultimately we want to move to making mixing of ports & > pkgs idiot-proof - something I suspect we're in better shape to do with > pkgng. As a recently minted roadtester of pkgng and wanting to do the > same as Vitaly without setting up Poudriere, I had to reverse engineer > the ports tree svn revision to make sure I could mix and match from > pkgbeta and stuff I built locally via ports with WITH_NEW_XORG and > WITH_KMS. This becomes more annoying to manage going forward. > > So far I'm enjoying my pkgng experience for the most part and wish to > thank all those involved in getting it to this stage. > > Cheers, > Lawrence What would be needed is a mechanism to query a package repository for a package with both name and options used to compile the package. Let's say you have a port installed that requires another port but that other port must be compiled with a certain option turned on. The packaging system should be able to tell if the package available from the remote repository satisfies the requirements or not. The current system accepts any version of the package because it only looks at the package name.