pkgsrc-Changes archive

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

Re: CVS commit: pkgsrc/pkgtools/bootstrap-mk-files/files

Alan Barrett <> writes:

> On Wed, 13 Mar 2013, Tim Zingelman wrote:
>>This breaks the bootstrap for solaris.
>>/bin/sh on solaris cannot handle the construct...
>># : ${OPSYS:=$(uname)}
>>syntax error: `(' unexpected
> pkgsrc/pkgtools/bootstrap-mk-files/Makefile should probably use
> REPLACE_SH to replace the interpreter on the #! line in
> .../files/  Then it would not be run using /bin/sh
> on Solaris.

bootstrap uses this script directly, bmake doesn't exist by then.

>>But, also...
>># id -un 0
>>id: illegal option -- u
>>Usage: id [-ap] [user]
>># id -gn "root"
>>id: illegal option -- g
>>Usage: id [-ap] [user]
> This is duplicating work that was already done by
> pkgsrc/bootstrap/bootstrap on most platforms.

No, this is not duplication of work.

> Is there already
> some way of accessing those results?

No, results of bootstrap are unavailable when you don't use bootstrap.

> If not, then it may be
> reasonable to add a way for relevant variables to be provided by
> infrastructure in pkgsrc/mk/**, with a way for /etc/mk.conf (or
> equivalent) to override them, and with a way for the pkgsrc
> bootstrap script to store appropriate values in mk.conf.

How does this help when pkgsrc/mk/** are not used at all?

Just to remind, we're talking about the case of building bmake and
accompanying mk files _without_ anything else from pkgsrc framework.
You cannot expect people who need only bmake to pull the whole framework.


Home | Main Index | Thread Index | Old Index