From owner-freebsd-current@FreeBSD.ORG Sun Apr 11 09:49:11 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0E05106564A for ; Sun, 11 Apr 2010 09:49:11 +0000 (UTC) (envelope-from sweetnavelorange@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 4A31B8FC1A for ; Sun, 11 Apr 2010 09:49:10 +0000 (UTC) Received: by vws17 with SMTP id 17so2529592vws.13 for ; Sun, 11 Apr 2010 02:49:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6ZPuKcT7gF6pk6G0qraFzryOnuffkpNJaomeo29v76k=; b=SkeiqhHfyfHxuRQt7k084otmrPYxnEeNMieW2oq99wI94dENsMNMUTNHaGmVXJxLjQ WOy45XMUWvcW58srPacaF97hzhwrT/fXqiQzsNPZ9+Sy5JPoG0owb2bxRUpM7nUCkRkJ 2OKMeMqKJThUefNyXqMw54oBsm4h5H8Hi19SQ= 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:content-transfer-encoding; b=NH8LcOWX0yLNS7NVp8qOVCNUz87S/cSQTxbgZcAWkpw2Hmt1YscfCt7HHK1vBaibkg blSD3/djEjZKELuDXc+YRp6UUHtlk64DafNZUynmkKwQA61C8+a8Ouez1e5bw8pB+AeX V2VNBWPn6xraJNT5Gtzc0kTmwSDTjDQsC3IyI= MIME-Version: 1.0 Received: by 10.229.106.229 with HTTP; Sun, 11 Apr 2010 02:49:09 -0700 (PDT) In-Reply-To: <4BC0CC6F.7010009@freebsd.org> References: <4BBFD502.1010507@elischer.org> <4BC03ABA.6090309@elischer.org> <4BC0CC6F.7010009@freebsd.org> Date: Sun, 11 Apr 2010 21:49:09 +1200 Received: by 10.220.62.141 with SMTP id x13mr1168150vch.224.1270979349989; Sun, 11 Apr 2010 02:49:09 -0700 (PDT) Message-ID: From: James Butler To: Tim Kientzle Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Sun, 11 Apr 2010 11:57:34 +0000 Cc: Adam Vande More , Kris Moore , John Hixson , "ports@freebsd.org" , Julian Elischer , "Dave Fourman\(Gmail\)" , "Sam Fourman Jr." , Garrett Cooper , Matt Olander , Vanessa Kraus , FreeBSD Current 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: Sun, 11 Apr 2010 09:49:11 -0000 On Sunday, April 11, 2010, Tim Kientzle wrote: > Garrett Cooper wrote: > > If I'm understanding you correctly you're saying it's an issue when I do: > > pkg_add A B C > > # 1 year passes > > pkg_add D > > # D depends on A, B, C, of different revisions. pkg_add barfs because > it can't find the applications, etc. > > This is something that's been hashed over a number of times (a few of > which I've participated in in #bsdports). There needs to be a simple > update command which will handle the action of upgrading packages, > because there isn't a proper command that will do so today. > > > I'm not convinced that the "simple update command" you > mention is actually feasible, much less desirable. > (If I want to try out the new Firefox, why does that > imply that my year-old Gimp has to be upgraded?) > > As for feasibility, here's the easy problem: > =C2=A0 A2.7 requires B3.6 > =C2=A0 =C2=A0 ... one year passes ... > =C2=A0 A4.8 now requires B7.2 > But A4.8 is incompatible with B3.6 and A2.7 is > incompatible with B7.2. =C2=A0So neither A nor B > can be updated separately without breaking the system. > > Here's the hard problem: > =C2=A0 A2.7 requires B3.6 > =C2=A0 =C2=A0 ... one year passes ... > =C2=A0 I want to install C1.0 which requires B7.2 > =C2=A0 but there hasn't been a new release of A that > =C2=A0 works with B7.2. > So I now simply cannot have both C1.0 and A2.7 > installed at the same time because they require > different versions of B. > > PBI avoids both of these problems. =C2=A0It may > be unsuitable for embedded systems[1], but > I see no reason we should not extend the existing > ports/packages system with additional tools that > target certain use cases, and PBI seems a good > fit for the desktop case. > > Tim 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? -James Butler > [1] Actually, PBI might work just fine even for > embedded if we address the disk bloat issue. =C2=A0One > approach would be to make > =C2=A0 /Package/Bar/libfoo-2.8.7.so > a symlink or hardlink to > =C2=A0 /Package/Shared/libfoo-2.8.7.so- > This gives easy sharing of identical files. > It's even easy to handle at install time: > =C2=A0* Installer writes libfoo-2.8.7.so to > =C2=A0 =C2=A0 /Package/Shared/libfoo-2.8.7.so-temp- > =C2=A0* Installer computes hash of file as it's written > =C2=A0* Installer renames file (delete if rename fails with EEXIST) > =C2=A0* Installer writes symlink or hardlink into /Package/Bar > > _______________________________________________ > freebsd-current@freebsd.org=C2=A0mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >