On 3/9/08, Vincent Manis [EMAIL PROTECTED] wrote:
2. Consider Chicken itself to be an egg. No, I don't mean some sort of
weird meta-thinginess involving building via chicken-setup, but just
initialize the repository when Chicken is installed to hold one egg,
for the system itself. Then eggs
Okay, I see what you mean now. I think it might be possible to
introduce separate actions or stages in chicken-setup, but I do not
want to make any more changes right now, because I need to deal with
the side-effects of introducing the -install-prefix option.
I believe it would be easy to
On 09/03/2008, Ivan Raikov [EMAIL PROTECTED] wrote:
Okay, I see what you mean now. I think it might be possible to
introduce separate actions or stages in chicken-setup, but I do not
want to make any more changes right now, because I need to deal with
the side-effects of introducing the
I'd like to suggest two changes to the release management process that
would make everyone's life easier.
1. Change the numbering system so that it includes a serial `build
number';
thus release 3.0.2 might be renumbered as 3.0.2/1073 (I chose the
slash so
that a build number wouldn't look
On 07/03/2008, Ivan Raikov [EMAIL PROTECTED] wrote:
I will look at the tinyclos egg, but I think you should use
-install-prefix for what you are trying to do. I have started using
that for my Debian scripts and so far it seems to work well. I haven't
tried anything with tinyclos yet,
On 02/03/2008, Ivan Raikov [EMAIL PROTECTED] wrote:
What you are referring to is the _Chicken_ install prefix,
i.e. where the Chicken executables are installed. What I am referring
to, is the user _install_ prefix, for situations where you would like
have the eggs in a separate
I will look at the tinyclos egg, but I think you should use
-install-prefix for what you are trying to do. I have started using
that for my Debian scripts and so far it seems to work well. I haven't
tried anything with tinyclos yet, though. The idea is that you should
_not_ have to add any
shouldnt it be installed to INSTALL_SHARE_HOME ?
which is settable at compile time, iirc, and saved in the chicken-config.h
file...
-elf
On Thu, 28 Feb 2008, Ivan Raikov wrote:
Yes, several other eggs do that, including one of
mine. chicken-setup exports a variable
YES
theres already a variable set in the chicken-config.h global include file
for this sort of thign, specifically, that SHOULD have been passed in at
runtime.
-elf
On Thu, 28 Feb 2008, Ivan Raikov wrote:
In that case, I believe all that needs to be done is to modify
copy-file and
I'm having issues with the tinyclos egg ebuild, chicken-setup is not
respecting the path I'm feeding it after '-R'... is this a bug, or by
design?
Cheers,
Leo
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
On 27/02/2008, John Cowan [EMAIL PROTECTED] wrote:
Leonardo Valeri Manera scripsit:
* Installing documentation files in
/var/tmp/paludis/dev-chicken/tinyclos-200801162015/work/tinyclos-200801162015/install:
cp -r tinyclos.html
On 28/02/2008, Ivan Raikov [EMAIL PROTECTED] wrote:
Yes, several other eggs do that, including one of
mine. chicken-setup exports a variable installation-prefix, which can
be used in .setup files ( I think), but someone needs to rewrite the
misbehaving setup files. Alternatively, I can
I was wrong about that, the value of CHICKEN_REPOSITORY is accessed
through the parameter repository-path, and the -R option works as
expected. But if -destdir is specified, then the repository becomes
{destdir}/lib/chicken. -destdir always overrides the repository path,
hence the confusion. I
On Thu, Feb 28, 2008 at 8:06 AM, Ivan Raikov [EMAIL PROTECTED] wrote:
I was wrong about that, the value of CHICKEN_REPOSITORY is accessed
through the parameter repository-path, and the -R option works as
expected. But if -destdir is specified, then the repository becomes
14 matches
Mail list logo
