Given that all the old tags are kept in the svn repository, wouldn't
chicken-setup be much better of installing chicken eggs directly from
it, in the case where the last release is not the desired one?
Note that it should only do this in the case where the last release is
not the desired one
On Tue, Feb 26, 2008 at 11:28 AM, Peter Bex [EMAIL PROTECTED] wrote:
This means you need an egg file for every egg release. Chicken-setup will
fetch the latest egg it can find *with compatibility for your chicken
version*,
as stated by the meta file. It would be an error if bar turns
I have added checks for TMPDIR and TEMPDIR. I do have TMP set in my
environment, but it turned out this is something I have added, not
part of the standard user environment. If anyone has suggestions about
other environment variables that specify temporary directory, I can
add those, too.
If
On Tuesday 26 February 2008 02:04:13 am felix winkelmann wrote:
I'm looking for proposals about how to find the ultimate
repository/packaging combination, or better: what could we do to keep a
central, revision controlled repository of chicken extensions, manage
chicken+extension
On Tue, Feb 26, 2008 at 2:35 PM, Matthew Welland [EMAIL PROTECTED] wrote:
On Tuesday 26 February 2008 02:04:13 am felix winkelmann wrote:
I'm looking for proposals about how to find the ultimate
repository/packaging combination, or better: what could we do to keep a
central, revision
On Feb 26, 2008, at 5:26 AM, felix winkelmann wrote:
Hi!
Regarding the repository question:
I'm getting bored.
I sympathize.
But the suggestion of specific version info in .meta is probably
good. So would be a common version format - suggest #.#.# since it is
very common used by
On Tue, Feb 26, 2008 at 2:42 PM, Ivan Raikov [EMAIL PROTECTED] wrote:
As I am preparing to resume work on Debian packaging, I would prefer
that there will be no radical changes to the egg SVN repository for
the time being, because the reorganization into release branches
already wasted
I don't know much about CPAN, as I've never learned Perl, but I know a lot of
people think it's really great.
Since, from what I gather, the eggs repository is roughly based on CPAN anyway,
why don't we copy CPAN further?
CPAN doesn't use a revision control system. Every* module is commited
On Feb 26, 2008, at 2:30 AM, Jim Ursetto wrote:
Hi core hackers,
Please consider this TCP patch, which speeds up the output port a
LOT; the
larger the write, the bigger the speedup.
snip
I will apply this if no one has objections.
Best Wishes,
Kon
