chicken-hackers
[Top][All Lists]
Advanced

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

Re: [Chicken-hackers] [PATCH] A native scheme install


From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH] A native scheme install
Date: Tue, 29 Jan 2013 09:18:48 +0100
User-agent: Mutt/1.4.2.3i

On Tue, Jan 29, 2013 at 12:50:11AM +0100, Michele La Monaca wrote:
> As I pointed out in a previous post, not all systems ship with a
> BSD-compliant "install" command. The usual way to overcome this
> problem is to provide an install.sh shell script.
> 
> I think chicken is in a better position being able to provide a native
> install.scm scheme program. That's exactly what the patch does: it
> adds a new library function (file-install) and the program install.scm
> which mimics a BSD install command.

Doesn't this create a bootstrapping problem while installing Chicken?
Chicken needs a working install to install the runtime system, but
your install needs the runtime system to be able to run...

> If it turns out to be a good idea, it would be feasible to switch to
> install.scm for every platform (Windows as well?). The advantage in
> doing so, aside from less customized build scripts and Makefiles, is a
> more robust and consistent build environment (in my opinion of
> course).

This would be nice to have, indeed.  But at what cost?

> Btw, the patch includes my previous patch for file=? because
> file-install needs it.

This seems unneccessary to me.  A BSD install simply always overwrites
a file (unless -b is given and it will unconditionally backup the file).

Cheers,
Peter
-- 
http://sjamaan.ath.cx



reply via email to

[Prev in Thread] Current Thread [Next in Thread]