unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org, 28004@debbugs.gnu.org
Subject: Re: Chromium channel
Date: Mon, 17 Sep 2018 16:16:43 +0200	[thread overview]
Message-ID: <87pnxccipg.fsf@lassieur.org> (raw)
In-Reply-To: <87efdsp820.fsf@fastmail.com>

Marius Bakke <mbakke@fastmail.com> writes:

> Clément Lassieur <clement@lassieur.org> writes:
>
>> Clément Lassieur <clement@lassieur.org> writes:
>>
>>> Hello :-)
>>>
>>> Ludovic Courtès <ludo@gnu.org> writes:
>>>
>>>> Hello,
>>>>
>>>> Clément Lassieur <clement@lassieur.org> skribis:
>>>>
>>>>> So the question is: can we push the Chromium package?  I've read it's
>>>>> almost ready[2].  It's probably far better than everything we have,
>>>>> despite not being totally 'finished'.  Maybe we can add what's left to
>>>>> do as a TODO and fix the package later?
>>>>
>>>> As long as the freedom issues and phone-home issues are addressed, which
>>>> appears to be the case, I’m all for it.
>>>>
>>>> Marius?
>>>
>>> Marius, what is the status, can we merge it?
>>
>> Ping
>
> Hello, sorry for the delay.
>
> I've set up a channel for Chromium here:
>
> https://gitlab.com/mbakke/guix-chromium
>
> Chromium has been updated for version 69 as well.
>
> I don't think we can merge as-is due to the tight Web Store integration
> (even if it's disabled), but I will start work on packaging the full
> "Ungoogled-Chromium" next:
>
> https://github.com/Eloston/ungoogled-chromium
>
> I'll bump this thread once it is ready for testing.  Developments will
> happen in the Gitlab repository.  Pull requests welcome!  :-)

Great!

Thank you very much Marius, and sorry for insisting.  The 'channels'
solution seems to fit very well!

Clément

  reply	other threads:[~2018-09-17 14:16 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  9:03 Firefox 52's end of life, packaging Chromium Clément Lassieur
2018-08-29 15:24 ` Pierre Neidhardt
2018-08-29 16:14 ` Christopher Lemmer Webber
2018-08-29 18:16 ` Leo Famulari
2018-08-29 21:25 ` Amirouche Boubekki
2018-08-29 22:35   ` Clément Lassieur
2018-08-29 23:26     ` Amirouche Boubekki
2018-08-30  7:43       ` Clément Lassieur
2018-08-30  1:12 ` Mike Gerwitz
2018-08-30  5:14   ` Clément Lassieur
2018-08-30  9:55     ` Ludovic Courtès
2018-08-30 10:04       ` Nils Gillmann
2018-08-30 11:01         ` Clément Lassieur
2018-08-30 12:09         ` Ludovic Courtès
2018-08-30 13:30           ` Nils Gillmann
2018-08-30 11:00       ` Clément Lassieur
2018-08-30 16:35     ` Mike Gerwitz
2018-08-30  9:07   ` Nils Gillmann
2018-08-30  9:20     ` Nils Gillmann
2018-08-30 16:38     ` Mike Gerwitz
2018-08-30  8:41 ` Ricardo Wurmus
2018-08-30  8:54   ` Clément Lassieur
2018-08-30 12:11     ` Ricardo Wurmus
2018-08-30 14:23   ` Amin Bandali
2018-09-01 14:08     ` Ludovic Courtès
2018-09-01 17:31       ` Nils Gillmann
2018-09-01 20:28         ` Amin Bandali
2018-09-02 13:54           ` Marius Bakke
2018-09-02 16:21             ` Mark H Weaver
2018-09-01 17:53     ` Joshua Branson
2018-09-01 23:18       ` Nils Gillmann
2018-09-03 20:57         ` Joshua Branson
2018-09-04  8:13           ` Nils Gillmann
2018-09-02  5:33   ` Mark H Weaver
2018-09-02  6:35     ` Mark H Weaver
2018-09-02  8:13       ` Mark H Weaver
2018-09-02 10:21       ` Ricardo Wurmus
2018-09-02 13:29         ` Marius Bakke
2018-09-02 16:48           ` Ricardo Wurmus
2018-09-04 21:44       ` Ludovic Courtès
2018-09-02  6:52     ` Leo Famulari
2018-08-30  9:57 ` Ludovic Courtès
2018-09-07  9:29   ` Clément Lassieur
2018-09-15 10:36     ` Clément Lassieur
2018-09-17 13:28       ` Chromium channel Marius Bakke
2018-09-17 14:16         ` Clément Lassieur [this message]
2018-09-17 18:08           ` Nils Gillmann
2018-09-17 17:57         ` Pjotr Prins
2018-09-22 12:44         ` 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=87pnxccipg.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=28004@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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).