Michele La Monaca writes:
>> Concurred, there is basically no way this change is going in as long
>> as it involves relying on Chicken before it is installed. 'make test'
>> doesn't even work in that case right now.
>>
>> Anyway, my understanding is that the existing solution works on all
>> kno
Sounds reasonable to me as well. I will provide the patch.
Nice discussion.
night!
mikele
On Tue, Jan 29, 2013 at 9:17 PM, Jim Ursetto wrote:
> On Jan 29, 2013, at 2:07 PM, Felix wrote:
>
>> From: Jim Ursetto
>
>>> Here's my humble suggestion: Move your file-install and file=? code
>>> directl
>> None of us uses this system. We can't find problems in or maintain an
>> installation program that's used only on platforms we don't have
>> access to.
>
> That's why Michele is proposing an alternative, I think.
That was exactly my main motivation. You can support only as many
platforms, but
If you can demonstrate that some core code (such as chicken-install)
would be improved with the addition of file-install then it might
be worth adding to core (probably in setup-api though).
I still think putting the file-install code in install.scm is
a better solution for that particular script
On Jan 29, 2013, at 2:07 PM, Felix wrote:
> From: Jim Ursetto
>> Here's my humble suggestion: Move your file-install and file=? code
>> directly into your install.scm script, and we'll make the install.scm
>> script available from the downloads page as an option.
>
> Well, we could also just ad
From: Jim Ursetto
Subject: Re: [Chicken-hackers] [PATCH] A native scheme install
Date: Tue, 29 Jan 2013 13:01:36 -0600
> On Jan 29, 2013, at 12:55 PM, Michele La Monaca wrote:
>
>> Ehi, I am not saying let's switch to install.scm as the default
>> installer (no
> On Tue, Jan 29, 2013 at 07:55:10PM +0100, Michele La Monaca wrote:
>> On some systems, Solaris 11 for
>> example, you don't have one in the default installation and the
>> current default (ginstall) is rather unlikely. That's it.
>
> None of us uses this system. We can't find problems in or ma
From: Michele La Monaca
Subject: Re: [Chicken-hackers] [PATCH] A native scheme install
Date: Tue, 29 Jan 2013 19:55:10 +0100
>> Concurred, there is basically no way this change is going in as long
>> as it involves relying on Chicken before it is installed. 'make test'
&
> Well, your proposition also includes adding a bunch of code to the
> files unit (that relies on unit posix, which is likely
> a no-go in and of itself).
>
> Here's my humble suggestion: Move your file-install and file=? code
> directly into your install.scm script, and we'll make the install.scm
On Jan 29, 2013, at 12:55 PM, Michele La Monaca wrote:
> Ehi, I am not saying let's switch to install.scm as the default
> installer (not for now at least). My proposition is: let's bundle
> install.scm in the tarball and let's give the user an extra chance to
> have a BSD-compatible install progr
On Tue, Jan 29, 2013 at 07:55:10PM +0100, Michele La Monaca wrote:
> On some systems, Solaris 11 for
> example, you don't have one in the default installation and the
> current default (ginstall) is rather unlikely. That's it.
None of us uses this system. We can't find problems in or maintain an
> Concurred, there is basically no way this change is going in as long
> as it involves relying on Chicken before it is installed. 'make test'
> doesn't even work in that case right now.
>
> Anyway, my understanding is that the existing solution works on all
> known platforms, while relying on uni
On Jan 29, 2013, at 11:20 AM, Michele La Monaca wrote:
> Anyway, you can always fall back to a
> different install program if needed. Just set INSTALL_PROGRAM to your
> favorite install command.
Which is why the existing solution works fine.
> No need to patch Makefiles to try. Just:
>
> LD_LIB
On Jan 29, 2013, at 9:35 AM, Peter Bex wrote:
> On Tue, Jan 29, 2013 at 04:15:13PM +0100, Michele La Monaca wrote:
>>> 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 sys
> On many systems this requires extra jumping through hoops like messing
> with LD_LIBRARY_PATH to make it find the runtime library when it's not
> in the installed location yet. Or building this install program
> statically.
>
> Also important: What happens in a cross-build environment?
Nothing
On Tue, Jan 29, 2013 at 04:35:07PM +0100, Peter Bex wrote:
> On Tue, Jan 29, 2013 at 04:15:13PM +0100, Michele La Monaca wrote:
> > > Doesn't this create a bootstrapping problem while installing Chicken?
> > > Chicken needs a working install to install the runtime system, but
> > > your install nee
On Tue, Jan 29, 2013 at 04:15:13PM +0100, Michele La Monaca wrote:
> > 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 the build succee
On Tue, Jan 29, 2013 at 04:15:13PM +0100, Michele La Monaca wrote:
> > 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 the build succee
> 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 the build succeeds you have your runtime system under your feet. If
the build fails you've go
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 be
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
21 matches
Mail list logo
