From owner-freebsd-ports@FreeBSD.ORG  Tue Jun 26 08:38:57 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 2ABF5106564A
	for <freebsd-ports@freebsd.org>; Tue, 26 Jun 2012 08:38:57 +0000 (UTC)
	(envelope-from mva@FreeBSD.org)
Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de
	[80.67.31.97]) by mx1.freebsd.org (Postfix) with ESMTP id D96628FC15
	for <freebsd-ports@freebsd.org>; Tue, 26 Jun 2012 08:38:56 +0000 (UTC)
Received: from [80.67.16.115] (helo=webmailfront01.ispgateway.de)
	by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.68) (envelope-from <mva@FreeBSD.org>) id 1SjRDk-00046x-Em
	for freebsd-ports@freebsd.org; Tue, 26 Jun 2012 10:34:00 +0200
Received: from 83.246.65.147 ([83.246.65.147]) by webmail.df.eu (Horde
	Framework) with HTTP; Tue, 26 Jun 2012 10:34:00 +0200
Date: Tue, 26 Jun 2012 10:34:00 +0200
Message-ID: <20120626103400.Horde.8frYBVNNcXdP6XP4ZP-0deA@webmail.df.eu>
From: Marcus von Appen <mva@FreeBSD.org>
To: freebsd-ports@freebsd.org
References: <4FE8E4A4.9070507@gmail.com>
	<20120626065732.GH41054@ithaqua.etoilebsd.net>
	<20120626092645.Horde.HytQbVNNcXdP6WQ1aMtjoMA@webmail.df.eu>
	<4FE96BA0.6040005@infracaninophile.co.uk>
In-Reply-To: <4FE96BA0.6040005@infracaninophile.co.uk>
User-Agent: Internet Messaging Program (IMP) H4 (5.0.19)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
X-Df-Sender: ZnJlZWJzZEBzeXNmYXVsdC5vcmc=
Subject: Re: Port system "problems"
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jun 2012 08:38:57 -0000

Matthew Seaman <m.seaman@infracaninophile.co.uk>:

> On 26/06/2012 08:26, Marcus von Appen wrote:
>>>> 1. Ports are not modular
>
>>> What do you mean by modular? if you are speaking about subpackages it
>>> is coming,
>>> but it takes time
>
>> I hope, we are not talking about some Debian-like approach here (foo-bin,
>> foo-dev, foo-doc, ....).
>
> Actually, yes -- that's pretty much exactly what we're talking about
> here.  Why do you feel subpackages would be a bad thing?

Because it makes installing ports more complex, causes maintainers to rip
upstream installation routines apart, and burdens users with additional tasks
to perform for what particular benefit (except saving some disk space)?

If I want to do some development the Debian way, I would need to do the
following:

- install foo-bin (if it ships with binaries)
- install foo-lib (libraries, etc.)
- install foo-dev (headers, etc.)
- install foo-doc (API docs)

With the ports I am currently doing:

- install foo

What are the requirements, use cases and benefits for splitting up packages
in such a way?
How would it work with the ports infrastructure without making things more
complex for port maintainers and the different port installation scenarios, we
have?

Cheers
Marcus