|
From: | Philip McGrath |
Subject: | [bug#55030] [PATCH 00/30] gnu: elm: Update to 0.19.1. Add build system & importer. |
Date: | Sun, 1 May 2022 18:17:05 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 |
Hi, On 5/1/22 16:37, Ludovic Courtès wrote:
Philip McGrath <philip@philipmcgrath.com> skribis:+ (package + (name "elm-virtual-dom")[...]+ (properties '((upstream-name . "elm/virtual-dom")))))Could/should the importer infer the upstream name from the Guix name by default? That way, we’d only need to specify that property where the automatic Guix->upstream name mapping wouldn’t work.
It could, but the heuristics seemed a bit brittle. To pick a few examples: 1. elm-virtual-dom -> "elm/virtual-dom" 2. elm-explorations-markdown -> "elm-explorations/markdown" 2. elm-terezka-intervals -> "terezka/intervals"We could add a special case for the "elm-explorations/*" namespace, but at least one of the others would need an explicit property. I *think* most of the packages in the "elm/*" namespace are single-element (e.g. "elm/html"), so maybe we could require the property for e.g. "elm/virtual-dom" and "elm/project-metadata-utils" ...
-Philip
[Prev in Thread] | Current Thread | [Next in Thread] |