unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: "Guix Devel" <guix-devel@gnu.org>,
	"Nicolò Balzarotti" <anothersms@gmail.com>
Subject: Re: Should guix track package aliases?
Date: Tue, 26 May 2020 01:14:53 +0200	[thread overview]
Message-ID: <CAJ3okZ3Z72GLxtQmPwNDu8zR+z3NabxwKZ=uX=BLTvtN9B37XA@mail.gmail.com> (raw)
In-Reply-To: <CAFkJGRf20aaNctBqwAnJenh-TyWgbaHx+uxRgKcHb9+V0aNEkw@mail.gmail.com>

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


  reply	other threads:[~2020-05-25 23:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 20:18 Should guix track package aliases? Josh Marshall
2020-05-10  9:10 ` Nikita Gillmann
2020-05-10  9:57 ` zimoun
2020-05-10 12:13   ` Julien Lepiller
2020-05-10 13:33     ` zimoun
2020-05-10 18:16       ` Josh Marshall
2020-05-24 19:25         ` Josh Marshall
2020-05-25 10:41           ` zimoun
2020-05-25 11:57             ` Josh Marshall
2020-05-25 12:04               ` Nicolò Balzarotti
2020-05-25 14:20                 ` Josh Marshall
2020-05-25 21:57                   ` Vincent Legoll
2020-05-25 22:30                     ` Josh Marshall
2020-05-25 23:14                       ` zimoun [this message]
2020-05-25 23:19                         ` Josh Marshall
2020-05-10 10:08 ` Vincent Legoll
2020-05-10 12:53   ` zimoun
2020-05-28 16:27     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ3okZ3Z72GLxtQmPwNDu8zR+z3NabxwKZ=uX=BLTvtN9B37XA@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=anothersms@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=joshua.r.marshall.1991@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).