Re: [Chicken-hackers] [PATCH] Fix #1169 by first deleting and then writing egg-info files

Hi Peter, That seems fine to me, applied. I don't think it's worth trying to fix this in the 4.x line, so I've closed the ticket as fixed. Cheers, Evan ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org

Re: [Chicken-hackers] [PATCH] Add chicken.platform module (partially)

On Sat, Apr 22, 2017 at 4:29 PM, Peter Bex wrote: For example, we also define "machine-type" in chicken.platform, which to > me is a bit confusing: how does machine-type differ from the "processor" > entry in system-information's list? And why do we need the hostname > to

[Chicken-hackers] [PATCH] Add chicken.platform module (partially)

Hi all, Attached are two patches which move some stuff around and create the chicken.platform module. The commits should speak for themselves. While working on the patch, I noticed that provide and provided? are not really related to feature identifiers as such, and more to code loading, so I

Re: [Chicken-hackers] [Chicken-janitors] #1218: chicken-install may fail if TMPDIR is mounted noexec (depending on setup-file details)

Ubuntu-derived distributions now ship with /tmp mounted as noexec by default. This results in a chicken-install error that is difficult to diagnose by non-expert users. The remedy can be as simple as setting TMPDIR (but perhaps that should be prominently documented), an option that forces

Re: [Chicken-hackers] [Chicken-janitors] #1218: chicken-install may fail if TMPDIR is mounted noexec (depending on setup-file details)

On Sat, Apr 22, 2017 at 07:17:09AM -0700, Ivan Raikov wrote: > It considerably limits the effectiveness of distributing software > written in Chicken, because now users who are not familiar with its > peculiarities cannot simply run chicken-install. Could at least some > option be added so that

[Chicken-hackers] [PATCH] Fix #1169 by first deleting and then writing egg-info files

Hi all, I wanted to check if the new chicken-install fixed the bugs we moved to the chicken-5 milestone and noticed that #1169 is still an issue under the circumstance where a re-installation of an egg is done as root, after the egg had been installed by a user before. The fix is pretty simple

Re: [Chicken-hackers] chicken-5-new-egg-install branch

On Wed, Apr 12, 2017 at 01:18:27PM +0200, felix.winkelm...@bevuta.com wrote: > Hello! > > The new egg-installation stuff is now in a state that seems to be basically > usable and I wonder how to go on with this, as it is a bit of a hassle to keep > this branch in sync with the C5 master. Hello