From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun,  7 Mar 2010 14:57:03 -0500
To: lucio@proxima.alt.za, 9fans@9fans.net
Message-ID: <7ec7c8eb9f96e2fd2fdf04f466ee5a80@brasstown.quanstro.net>
In-Reply-To: <4dd387fd75c33dc431653175a6c71940@proxima.alt.za>
References: <4dd387fd75c33dc431653175a6c71940@proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [9fans] (no subject)
Topicbox-Message-UUID: e337e45e-ead5-11e9-9d60-3106f5b1d025

> Thing is, the "port" hierarchy (hereto I used "NetBSD package system"
> for the same concept) provides both the hierarchical structure I
> believe is needed to minimise duplication and a description file to
> search for concepts rather than file names.  So, yes, I agree with a
> portion of your suggestion, but not your suggested implementation.  In
> practice, all I'm proposing is replacing directories owned by
> individual contributors with a hierarchy that undergoes a useful
> amount of validation.

this is exactly the reason you need to try contrib.

if you want to make an überpackage, just make your
überpackage depend on everything else.  it doesn't
need to have any files of its own.  i've verified this.
it would be a trivial extension (like 2 lines) to have
contrib/install recursively install dependencies.

- erik