On Mon, Jul 03, 2006 at 01:33:58PM +0300, Aleksey Cheusov wrote:
> > I'm about to embark on a project I had mentioned briefly to some folks
> > while at pkgsrcCon this year -- I am going to split out the variables
> > and targets associated with the "install" and "package" phases from
> > bsd.pkg.mk into their own modules, e.g. bsd.pkg.{install,package}.mk.
> [skipped]
> > In my mind, pkgsrc does two
> > separate and distinct things, even though we just call the whole thing
> > "pkgsrc" -- pkgsrc is a system to build software, and pkgsrc is a
> > system to manage software.
> Before you or someone else adopt pkgsrc to make .deb or .rpm or
> whatever: what about adopting pkgsrc to make several packages for a
> single build process, for example,
> multimedia/mplayer -> mplayer & mencoder packages.
> 
> IMHO this ability is very convenient, especially for large projects
> like programming languages. For me, including
> ../../somewhere/common_dir/Makefile.common looks very strange.

Agreed.  I wouldn't mind so much about long build times if the resulting
binary packages were fine-grained enough to express accurate dependencies...

(Because in order to do that, you first need to build the whole package
with all features enabled and only afterwards construct different binary
packages based on the resulting files.)

-- 
Julio M. Merino Vidal <jmmv@NetBSD.org>