On Tue, Jun 05, 2007 at 07:09:06PM -0700, [EMAIL PROTECTED] wrote:
> As monolithic as it may be, when you're building an entire
> platform, something of that nature is required to deliver
> it all.  While it may be an unfamiliar task to Linux folks,
> it isn't to those from the BSD world.
> 
> Similar commands exist for FreeBSD - "make buildworld" - and
> NetBSD "make build" - that build the entire operating system,
> kernel, commands, man pages, etc.  However unlike Solaris,
> on both of those BSD platforms there is no extra special
> bits required.

I've runned OpenBSD and FreeBSD for many years, I know the difference
between the base system and ports/packages.

> If I want to build just a specific kernel module, I cd to
> usr/src/uts/intel/ip (for example, to build just ip) and
> type "make all" in that directory.
> 
> Similarly I can do a "make" in various other directories
> for libraries, binaries, etc.  However it isn't safe to
> build just in one place until after you've done a complete
> build as there may be dependencies, etc.
> 
> At least one "short cut" required if you wan to try building
> just a small part is to do a "make install_h" in usr/src.
> 
> Being able to do "make" in usr/src and have that invoke
> nightly or whatever would be "nice".

My point is: neither OpenBSD, FreeBSD, NetBSD provides a decent 
way to upgrade the core system AND packages at the same time. I love *BSD,
but I'm not running it on production server simply because you can't 
upgrade it quickly. On the other site, if the packaging system is
also aware of the base system and packages. That's all I request :)

PS: It seems I didn't read the build process correctly.

"Ordinary SVR4 packages can be built from the files installed into the
proto area (see section 4.4.1). This is done automatically by the main
makefile's all and pkg_all targets (see usr/src/Makefile) as part of a
successful build."

-- 
Francois Saint-Jacques
http://www.networkdump.com
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to