|
From: | Josh Marshall |
Subject: | Re: Should guix track package aliases? |
Date: | Mon, 25 May 2020 19:19:55 -0400 |
Dear Josh,
On Tue, 26 May 2020 at 00:31, Josh Marshall
<address@hidden> wrote:
> I could fix up some of the new homepages. We've already seen some Gnu related package losses like gdal. I think SWH adoption for packages may want to be moved from as packages are added to as packages are updated -- just to have a regular, low overhead, but still slow move to SWH.
What do you mean by "losses like gdal"?
BTW, if the method of package origin is 'git-fetch' then "guix lint"
should automatically queue the package to SWH. And I guess that the
Data Service or CI is linting, whatever the package is added or
updated.
The file 'sources.json' is updated every X minutes (or hours) and the
SWH fetcher should be ready really soon. And once this 'url-fetch'
from SWH is on production, a lot of packages will move to SWH.
Well, considering SWH, what is missing today IMHO on the Guix side is
UI, e.g., display using "guix weather" if the package is in SWH or
not, display a chart on the Data Service to represent which percentage
is in SWH, maybe move the {package,source}-json-builder from the
website engine to "guix publish", etc.. Help welcome. :-)
All the best,
simon
[Prev in Thread] | Current Thread | [Next in Thread] |