On Tue, Jul 22, 2008 at 2:44 PM, felix winkelmann <[EMAIL PROTECTED]> wrote: > On Tue, Jul 22, 2008 at 7:24 AM, Shawn Rutledge > <[EMAIL PROTECTED]> wrote:
>> Now for the next problem with this same egg: it requires eggdoc (the >> .meta file has (needs eggdoc ...)). I don't really want to install >> that on my phone. So I guess we need a way to distinguish >> compile-time requirements from runtime ones. > That is a job for next the generation of chicken-setup. IMHO eggdoc should never be a dependency of an egg, not even at compile-time. .html output should be checked into SVN to avoid the dependency. Instead an alternative might be: include the .html output in the egg, and in the .setup file, use the (make) macro to conditionally generate the .html via eggdoc. This should allow the developer to generate .html when the .scm source is updated, while avoiding the rebuild for end users. FWIW, I always just ran eggdoc manually. _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
