[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Naming (Re: Unified packages. )

On Sun, 20 Aug 2000, Adrian Filipi-Martin wrote:
> > We should take into consideration that bmake != /usr/bin/make of any BSD
> > system. make(1) seems to different on these systems, unfortunately. (Or so
> > I've heared, e.g. when it comes to variable modifiers: ${FOO:x...}
> 	Maybe I'm using the wrong name.  I mean the flavor of make that the
> the BSD's share.  Unless I'm mistaken they stem from one ancestor.  Correct
> me if I'm wrong.  

Type 'man make' on your favourite BSD system, go to the section of
variable expansion modifiers: ``The general format of a variable
expansion is as follows:


Now you'll find that (at least) FreeBSD does not offer ":C" (which is like
:S, just with patterns instead of fixed strings), while NetBSD has this,
and makes lots of usage of this. Working around that lack will mean
pulling out sed(1).

> 	I think we have two tasks at hand.  One is the makefile portion
> (fetching, patching, building,...) and the other is the binary package
> management tools (pkg_{create,add, ...etc}).  I agree that other packaging
> tools might be nice down the line.  Doesn't solaris use sw-tools like
> HP-UX? 

Maybe. In any case, tools exist to convert "NetBSD"-packages on Solaris to
native Solaris-pkgs.

 - Hubert

NetBSD - because Unix isn't just #include <linux.h>, i386, ILP32, ELF, ...!

To unsubscribe: send mail to <majordomo@unixathome.org>
with "unsubscribe bsdports" in the body of the message