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

[Aleksej Saushev <asau%inbox.ru@localhost>]

Alan Barrett <apb%cequrux.com@localhost> writes:

> On Wed, 20 Mar 2013, Aleksej Saushev wrote:
>>> pkgsrc/pkgtools/bootstrap-mk-files/Makefile should probably
>>> use REPLACE_SH to replace the interpreter on the #! line in
>>> .../files/bootstrap.sh.  Then it would not be run using
>>> /bin/sh on Solaris.
>>
>> bootstrap uses this script directly, bmake doesn't exist by
>> then.
>
> I guess "bootstrap" means "the bootstrap script inside
> bootstrap-mk-files", not "the pkgsrc bootstrap script".

No, bootstrap means pkgsrc bootstrap script here.
It is unclear why the script in bootstrap-mk-files is called
"bootstrap.sh" when it is just a build script.

>> 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.
>
> Really?  You are trying to build and install a pkgsrc package
> without using the normal pkgsrc infrastructure?  That was not at
> all clear to me.
>
> OK, if you insist on doing that, then you won't be able to
> re-use results that were already figured out by
> pkgsrc/bootstrap/bootstrap, but you can at least use the same
> techniques as are used there.

This requires a lot more time to implement, test, discuss, review, etc etc.
It is not ideal in the current form but it simplifies my life when helping with 
it.


-- 
BECHA...
   CKOPO CE3OH...