Re: Should guix track package aliases?

[Josh Marshall <joshua.r.marshall.1991@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

For gadl, it was that the gal website hosting it went down.  With regards
to pre-commit hooks, just to make sure each commit message conforms to what
is expected and is best practice for PRs and commits for the project.

On Mon, May 25, 2020, 19:15 zimoun <zimon.toutoune@gmail.com> wrote:

> Dear Josh,
>
> On Tue, 26 May 2020 at 00:31, Josh Marshall
> <joshua.r.marshall.1991@gmail.com> 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
>

[-- Attachment #2: Type: text/html, Size: 2057 bytes --]