From owner-freebsd-current@FreeBSD.ORG Mon May 3 19:55:18 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67B9C106566B for ; Mon, 3 May 2010 19:55:18 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 16C258FC16 for ; Mon, 3 May 2010 19:55:17 +0000 (UTC) Received: by vws7 with SMTP id 7so1812242vws.13 for ; Mon, 03 May 2010 12:55:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=X2i4H4pZBM4z7XcLAItBfXxHR3azeal6LmdwWD4IoE0=; b=PvOETxLjVReeYzbLh7AG7W+RX/qYRu4lmPU9vINhfJx1X+c8FVO/uG9SftJWDnwATv ujPoIGHEQ2YfxYj4f4HMXRywCDIYJrqDc3bFg7b9CABWf5IB8HsObqdMGzP2uYbzOSI/ gnzOSJc/oKRqe8XioMNifhVp8G0p83CpTbMg8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=trrK717zA3e1lZXna3mMWsaVTArP3PjJK+kZ+CMy/M1qQfvWf6c8USEXjY47Kq8s8e y3qWW3KncBZD2wEy71pRdHcTWhpzokKxXuPBI+/8dMM2uMnDnEHsmTimi58AMrqCli73 1+xvfwIv2tjKjeJlMfJwZRHDhuXkBWRTUeIAs= MIME-Version: 1.0 Received: by 10.229.186.212 with SMTP id ct20mr34692qcb.39.1272916517032; Mon, 03 May 2010 12:55:17 -0700 (PDT) Received: by 10.229.251.17 with HTTP; Mon, 3 May 2010 12:55:16 -0700 (PDT) In-Reply-To: <4BDEDECD.70508@pcbsd.org> References: <4BBFD502.1010507@elischer.org> <4BC03ABA.6090309@elischer.org> <4BC0CC6F.7010009@freebsd.org> <4BDEDECD.70508@pcbsd.org> Date: Mon, 3 May 2010 12:55:16 -0700 Message-ID: From: Garrett Cooper To: Kris Moore Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: ports and PBIs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2010 19:55:18 -0000 On Mon, May 3, 2010 at 7:33 AM, Kris Moore wrote: > On 05/01/2010 00:29, James Butler wrote: >> >> Genuine (possibly stupid) question -in PBI land, what happens if >> package B is, say, CUPS? Does one need versioned rc.d scripts to start >> one or the other? Which one gets to claim port 631? > > That is a problem we are dealing with right now. We have to check to ensure > that we don't already have a rc.d script for CUPS, and default to the > pre-existing one if so. The only other option I see is that we default to > the PBI one, but either way we can only have one copy running at a time :) Hi Kris, In general though, conflicting services or applications reading / touching files with version dependent data is going to be a difficult run for PBI based fat packages though, correct? This was one of the items that I brought up that was concerning in my previous questions, but it kind of got lost in the bikeshed portion of the discussion that I started with a few folks. My point is that just looking for one set of rc.d scripts might be oversimplifying the problem statement a bit; I understand that good applications should have an alternate configuration option at the very least, or should be modified (via some in-place sed action or something similar at install time) so that the default location is ${DBI_DESTDIR}/${PREFIX}/, correct? Also, for services like cups, there could have per-application virtualized networking stacks implemented per daemon (via vimage?) to circumvent this caveat, correct (cues Julian for the confirmation)? Or are shared jail(8) environments the only real means to solve this problem (probably not the correct nomenclature, but something conceptually similar to a shared jail built out of links pointing to the system binaries wherever possible and a series of shared ports libraries wherever not possible)? Thanks, -Garrett