Hi!
The toplevel eggs have now been moved into the release/2
directory. The post-commit code has been updated and seems to be running.
I've seen that there have been some commits during the time
of the reorganization. These commits have not resulted in egg updating, as
the automatic post commit
Hello,
wouldn't it be a solution if chicken-setup would downgrade its
priviliges to a regular user for everything but installation of files in
case it was run as root?
I would also suggest that chicken-setup should download, unpack and
compile eggs in a fresh temporary directory instead of
What is the general process for submitting changes? I have write
access to the subversion repository and I'd like to submit some
minor changes to rules.make, Makefile.msvc, and a one-line change
to library.scm, all to fix the MSVC build. Should I just
commit the changes? I saw a previous post
Hello,
If you want, post your patch to this mailing list before committing,
and I can make sure it doesn't break the Unix builds. I don't have
Windows or MSVC, so I cannot test the MSVC build, but at least I can
make sure there are no accidental breakages of something else.
-Ivan
Ashley
Hi all,
It seems that trac.callcc.org is down most of the time I try to
access it. Either I get a 500 error, or the HTTP request times out
after a very long time. Is this instability inherent in Trac, or is
there something peculiar about this particular installation? In either
case, we need to
Hi, everybody!
For those that use egg-post-commit on their personal checkouts:
the usage has slightly changed: the -cd option is implicit.
Generally I recommend not to use egg-post-commit as it
has many subtle dependencies and everything on galinha
is set up correctly.
A tasks file is loaded
On Mon, Feb 25, 2008 at 8:33 AM, Ivan Raikov [EMAIL PROTECTED] wrote:
Ok, will do. I will also add some optional privilege de-escalation
functionality for the unpack and compile phases, if it is easy to
implement.
Cool! I have to warn you, though: chicken-setup.scm is a real mess!
