chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] Proposed patch for destination egg property


From: felix . winkelmann
Subject: Re: [Chicken-hackers] Proposed patch for destination egg property
Date: Tue, 15 Jan 2019 00:22:39 +0100

> When porting chickadee to Chicken 5, I hit a roadblock when installing data 
> files into a namespaced directory — <PREFIX>/share/chicken/chickadee.
>
> In Chicken 4, we can execute code in .setup to obtain this directory — 
> (make-pathname (chicken-home) "chickadee”) — and use copy-file. In Chicken 5, 
> we can’t execute code in .egg files, and the (data) component copies files 
> directly into the shared directory.
>
> The destination property can override the install directory, but is only 
> defined for absolute paths, and you can’t compute the absolute shared path in 
> an .egg. (Also, chicken-install fails if the destination property is present.)
>
> There is a workaround for Chicken 5, where I can place all my data files into 
> a directory “chickadee” inside the egg “chickadee”, then specify chickadee as 
> the directory in the data component. Ugly, but effective.

In 5.0.1 (or somewhere between 5.0.0 and 5.0.1) this feature was explicitly
added, so the option given last above is what you should do (and I must say 
that I
don't find it particularly ugly). "destination" is actually rather useless and 
should
be removed, IMO.


felix




reply via email to

[Prev in Thread] Current Thread [Next in Thread]