From owner-freebsd-ports@FreeBSD.ORG Fri Oct 4 13:29:51 2013 Return-Path: Delivered-To: ports@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 ESMTP id 6DA74D21 for ; Fri, 4 Oct 2013 13:29:51 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F18722D33 for ; Fri, 4 Oct 2013 13:29:50 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id ex4so1650206wid.8 for ; Fri, 04 Oct 2013 06:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=IxDyRJYmXS0eDTTRBVLY+y6SxBF/DWfH+7gsTtW1DUY=; b=cS7Ym1jThz0ksEAbJ0quq+k99xDjHrXzF9Fov3h5ypjchD66OgrAZR2/h+nP74RRqc C+iZsaa4m67oxHk1xtwdRenTuD2Ayq9DF5OxxlZe8XwAXkUz78VOQcRVzxxHlm6SEbuj HdEiYa4VS7ig4mRZMUpkc7yIeoobQf4ML3QCqxLw2EHJOy0ZGoDtjBwqeiynydKvM/96 q3kbfX5LKqhdDErQiEP+9C1JGsbfwinTaSWDycXWuVNJotAawkqr7yube23SwJ4yz1Vf Ij0BRL4bRu3BAdrk2fIBlbVP245hkJ+kmqrtYkTRXDtbXVRjAjLaB0R4/mMYKDibIBPg qI1g== X-Received: by 10.180.76.48 with SMTP id h16mr7382414wiw.32.1380893389368; Fri, 04 Oct 2013 06:29:49 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id b11sm5206290wik.1.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 04 Oct 2013 06:29:48 -0700 (PDT) Sender: Baptiste Daroussin Date: Fri, 4 Oct 2013 15:29:45 +0200 From: Baptiste Daroussin To: Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: [HEADSUP] Staging, packaging and more Message-ID: <20131004132945.GL72453@ithaqua.etoilebsd.net> References: <20131003084814.GB99713@ithaqua.etoilebsd.net> <524D6059.2000700@FreeBSD.org> <524DD120.4000701@freebsd.org> <20131003203501.GA1371@medusa.sysfault.org> <20131004061833.GA1367@medusa.sysfault.org> <20131004063259.GC72453@ithaqua.etoilebsd.net> <524E679B.9010103@infracaninophile.co.uk> <20131004070503.GF72453@ithaqua.etoilebsd.net> <524EB31C.6060102@quip.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Bzq2cJcN05fcPrs+" Content-Disposition: inline In-Reply-To: <524EB31C.6060102@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@freebsd.org, Fernando =?iso-8859-1?Q?Apestegu=EDa?= X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2013 13:29:51 -0000 --Bzq2cJcN05fcPrs+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 04, 2013 at 02:22:52PM +0200, Miroslav Lachman wrote: > Baptiste Daroussin wrote: > > On Fri, Oct 04, 2013 at 08:00:43AM +0100, Matthew Seaman wrote: > >> On 04/10/2013 07:32, Baptiste Daroussin wrote: > >>> On the other ends, that makes the package fat for embedded systems, t= hat also > >>> makes some arbitrary runtime conflicts between packages (because they= both > >>> provide the same symlink on the .so, while we could live with 2 versi= on at > >>> runtime), that leads to tons of potential issue while building locall= y, and > >>> that makes having sometime insane issues with dependency tracking. Wh= y having > >>> .a, .la, .h etc in production servers? It could greatly reduce PBI si= ze, etc. > >>> > >>> Personnaly I do have no strong opinion in one or another direction. S= hould we be > >>> nicer with developers? with end users? with embedded world? That is t= he question > >>> to face to decide if -devel packages is where we want to go or not. > >> > >> Can't we have the best of both worlds? > >> > >> We're already planning on creating sub-packages for eg. docs and > >> examples. The default will be to install docs etc. sub-packages > >> automatically unless the user opts out in some way. I imagine there > >> will be a global switch somewhere -- in pkg.conf or similar[*]. > >> > >> Couldn't we work devel packages in the same way? Install by default > >> alongside the main package unless explicitly requested not to. > >> > >> I think having the capability to selectively install parts of packages > >> like this is important and useful functionality and something that will > >> be indispensible for eg. embedded platforms. But not an option that t= he > >> vast majority of ordinary users will need to exercise. > >> > >> Cheers, > >> > >> Matthew > >> > >> [*] The precise mechanism for choosing which sub-package bits to insta= ll > >> has not yet been written. If anyone has any bright ideas about how th= is > >> should all work, then I'd be interested to hear them. > >> > > > > That is another possiblity, I do prefer Erwin's idea about the -full, b= ut this > > also makes a lot of sense. >=20 > I really like the current state with full packages. Disk space is cheap,= =20 > full packages is default for whole FreeBSD existence and it is easy to=20 > maintain the system with it. If I want portA and portB, I just install=20 > portA and portB and if I want to see installed ports, I see two ports=20 > installed and not a bunch of lines like: > portA-bin > portA-doc > portA-dev > portB-bin > portB-doc > portB-dev >=20 > When I need to update those ports, I will update two ports, not six or=20 > more ports / sub ports. >=20 > Embedded systems are corner case, where many things need to be tweaked=20 > anyway. >=20 > So I like the idea of default full packages with possibility to=20 > optionally select and install sub parts for those who really need the=20 > fine grained list of packages. That is because you keep thinking you have to build those ports yourself, w= e are here speaking of binary packages. regards, Bapt --Bzq2cJcN05fcPrs+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlJOwskACgkQ8kTtMUmk6ExmIQCbBOZ6rj302chfnrCXxplHk89v CBEAnjV1UWGJtfUNh1B92VIdR8kZgcSI =9Uki -----END PGP SIGNATURE----- --Bzq2cJcN05fcPrs+--