Skip site navigation (1)Skip section navigation (2)
Date:      12 Apr 2000 18:43:51 -0700
From:      asami@FreeBSD.org (Satoshi - Ports Wraith - Asami)
To:        Marcel Moolenaar <marcel@cup.hp.com>
Cc:        Kris Kennaway <kris@FreeBSD.org>, ports@FreeBSD.org, marcel@FreeBSD.org
Subject:   Re: Fwd: linux ports (Re: Netscape 6 Linux pre-release, got it going.)
Message-ID:  <vqc3doqai7c.fsf@silvia.hip.berkeley.edu>
In-Reply-To: Marcel Moolenaar's message of "Wed, 12 Apr 2000 09:28:07 -0700"
References:  <Pine.BSF.4.21.0004112032120.78206-100000@freefall.freebsd.org> <vqcbt3fiy3x.fsf@silvia.hip.berkeley.edu> <38F4A417.CBDBD48D@cup.hp.com>

next in thread | previous in thread | raw e-mail | index | archive | help
 * From: Marcel Moolenaar <marcel@cup.hp.com>

 * I'm not (yet) on -ports. Thanks.

Ok.  You probably should be, though. :>

 * The linux_base port is supposed to install just enough packages to mimic
 * a RH base installation. It uses (supposed to use) as much native FreeBSD
 * tools as is compatibility-wise possible.
 * 
 * On top of that other packages can be installed that "extend" the base
 * installation. Currently only linux_devtools exists.
 * 
 * We've added X related rpms to linux_base because there was no point in
 * creating a linux_x11 port that only installs a single (or maybe 2) rpms.
 * I'm not in favor of adding too much X related packages to linux_base. I
 * prefer to create a new port that contains X "stuff" in that case.

Sure, that's fine.

 * The problem may be that we would have 2 systems that specify and use
 * dependencies; our ports collection and the rpms. Having a system that
 * works requires us to either 1) duplicate rpm dependencies into the ports
 * tree (=static) or 2) add a way to extract rpm dependencies from the
 * database/rpms on the fly (=dynamic).

I don't think the latter is going to work.  The dependencies have to
be static for INDEX and packages to function correctly.  We don't have
to upgrade the rpm dependencies that often anyway, I think duplicating
them in our ports framework is fine.

 * Having a way to download and install rpms that are required by a port
 * seems like a good idea. It avoids bloating linux_base or creating
 * additional ports (which only increases the overall complexity of setting
 * up /compat/linux).

I'm not sure exactly how the "download and install rpms" part is going
to work but I really like this to fit into our ports framework.  In
particular, I would like to have them build packages and have pkg_*
deal with them just like any other port.  Otherwise people trying to
install the system from CDs is going to be screwed.

-PW


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqc3doqai7c.fsf>