Changeset 35630 in project

Timestamp:

06/20/18 21:31:47 (9 months ago)

Author:

sjamaan

Message:

Also add a concrete example of .egg file porting

File:

• wiki/porting-c4-to-c5 (modified) (1 diff)

wiki/porting-c4-to-c5

@@ -334 +334 @@
 name, license and dependency declarations.  Added to this are
 "components", which make up the egg's sources.
+
+For simple eggs, this is also trivial.  Here's uri-generic's old
+{{.meta}} file:
+
+<enscript highlight="scheme">
+((egg "uri-generic.egg")
+ (license "BSD")
+ (category web)
+ (needs matchable)
+ (test-depends test)
+ (author "Ivan Raikov, Peter Bex, Seth Alves")
+ (synopsis "URI generic syntax (RFC 3986) parsing and manipulation."))
+</enscript>
+
+And its {{.setup}} file:
+
+<enscript highlight="scheme">
+(standard-extension 'uri-generic "2.43")
+</enscript>
+
+After porting this to CHICKEN 5's {{.egg}} file, you get:
+
+<enscript highlight="scheme">
+((license "BSD")
+ (category web)
+ (dependencies matchable srfi-1 srfi-13 srfi-14)
+ (test-dependencies test)
+ (author "Ivan Raikov, Peter Bex, Seth Alves")
+ (synopsis "URI generic syntax (RFC 3986) parsing and manipulation.")
+ (components (extension uri-generic)))
+</enscript>
+
+As you can see, for eggs consisting of a single file, this is very
+straightforward: just add any missing egg dependencies for the stuff
+that has moved out of core, remove obsolete forms like {{(egg ..)}},
+replace {{needs}} or {{depends}} with {{dependencies}}, replace
+{{test-depends}} to {{test-dependencies}} and add a {{(components
+(extension ..))}} entry which corresponds to {{standard-extension}}
+from the old {{.setup}} file.
+
+For more complex examples of {{.egg}} files, just look through the
+[[/chicken-projects/egg-index-5.html|list of available CHICKEN 5 eggs]].
+There are a few in there with multiple source files and even some with
+custom build scripts.