cvs commit: ports/emulators/linux_base-fc4 Makefile

[David O'Brien]

On Sat, Dec 22, 2007 at 01:36:27PM +0100, Alexander Leidinger wrote:
> Quoting David O'Brien <obrien at FreeBSD.org> (from Thu, 20 Dec 2007 08:34:02 
> -0800):
>> On Thu, Dec 20, 2007 at 09:23:55AM +0100, Alexander Leidinger wrote:
>> This change does make it so one can add the right linux_base.  Without
>> it, one must go churning thru /usr/ports/Mk/bsd.port.mk to figure out
>> what specific distro is the right app.
> 
> This is only true if you want to add it by hand, instead of letting the
> pkg tools tell you which one to download. What I would like to know is,
> if you are adding it by hand and then using a linux program which is
> not available as a port, or if you install a linux program from
> ports/pkg by installing all the prerequisite by hand.

Both.
The last time I 'pkg_add -r'ed linux_base it was to run company internal
applications that aren't a FreeBSD package.

At times I also like to pre-install some dependencies - to make it easier
to monitor the install of the application I'm ultimately interested in.

> I'm asking this, because normally it doesn't make sense to install
> linux programs as packages. The ports download binary files anyway, and
> there's no compiling or some other time consuming operation happening.

Sure it does - it is faster to 'pkg_add -r linux_base' than "build" it
from /usr/ports - where one has to download 36 files.  Especially if the
first MASTER_SITE listed isn't having a good day.

> In most of the cases installing a linux base by hand is the wrong thing
> to do.

That is a very personal POV.  I see nothing wrong with it.  Expecially if
one is scripting the installation of several FreeBSD boxes.  And if we do
a proper job of keeping "linux_base" pointing to the right package, this
line in Sysinstall doesn't have to keep changing to chase our
advancements:
    config.c:    i = package_add("linux_base-fc");

-- 
-- David  (obrien at FreeBSD.org)