Hi Pierre,
Pierre Neidhardt <m...@ambrevar.xyz> skribis:
> Examples:
>
> - `("foo/bar" "share/my-app/")`: Install bar to "share/my-app/bar".
> - `("foo/bar" "share/my-app/baz")`: Install bar to "share/my-app/baz".
> - `("foo/" "share/my-app")`: Install the content of foo inside "share/my-app",
> e.g. install "foo/sub/file" to "share/my-app/sub/file".
> - `("foo/" "share/my-app" #:include ("sub/file"))`: Install only
> "foo/sub/file" to "share/my-app/sub/file".
> - `("foo/sub" "share/my-app" #:include ("file"))`: Install "foo/sub/file" to
> "share/my-app/file".
Looks like it could work.
I think the general approach should be: pick a handful of packages that
you’d like to rewrite to the new build system, provide the options that
support it (but not more), and verify that the resulting package
definitions are indeed shorter.
> Maybe instead of having two #:include and #:include-regexp we could have just
> one #:include in which the list elements have a "marker" that tells whether
> they
> are regexps or not.
Probably the former, so that strings are either always or never
interpreted as regexps. (Guile doesn’t have special “markers” for
regexps.)
Ludo’.
