unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ngillmann@runbox.com>
To: Efraim Flashner <efraim@flashner.co.il>,
	Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: texmaker, Qt and Chromium
Date: Sat, 08 Oct 2016 21:20:42 +0000	[thread overview]
Message-ID: <87mvieillh.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20161008210850.GB18485@macbook42.flashner.co.il>

Efraim Flashner <efraim@flashner.co.il> writes:

> [ Unknown signature status ]
> On Sat, Oct 08, 2016 at 11:00:29PM +0200, Ricardo Wurmus wrote:
>> 
>> Efraim Flashner <efraim@flashner.co.il> writes:
>> 
>> > AFAIK Chromium doesn't modify any of its bundled software. Would it make
>> > sense to create a chromium-source package that replaces the bundled
>> > sources with our sources, allowing us to keep the chromium source and
>> > the bundled source up-to-date. Then we could use this new
>> > 'chromium-source' package as a replacement source for
>> > chromium/inox/qtwebengine?
>> 
>> Are you certain they don’t modify their bundle?  I thought that was the
>> whole point for them to bundle things in the first place: to be able to
>> modify things without having to coordinate with the various upstreams.
>> 
>> ~~ Ricardo
>> 
>
> I'm not sure, but I assumed it was so that anyone could download the
> source and run './configure; make; (sudo) make install' without worrying
> about those pesky things known as dependancies.
>
> -- 
> Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
> GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted

As far as I know - I could be wrong - I linked to the bug ticket for
unbundling chromium in my inox.scm ... Fedora got so frustrated over
the whole, well... neglection.. of the ticket that they forked
chromium. I would say at best it (unbundling) just works, but not with
all of the dependencies/bundles as far as I understand comments Gentoo
and Archlinux do in their chrome/chromium/inox related packages.

  reply	other threads:[~2016-10-08 21:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 19:17 texmaker, Qt and Chromium Ricardo Wurmus
2016-10-08  8:14 ` Roel Janssen
2016-10-08  9:18   ` Ricardo Wurmus
2016-10-08  9:35     ` David Craven
2016-10-08  9:45       ` Ricardo Wurmus
2016-10-08  9:50         ` David Craven
2016-10-08 22:09     ` Leo Famulari
2016-10-08  8:21 ` John Darrington
2016-10-08  8:55 ` Danny Milosavljevic
2016-10-08  9:16   ` Ricardo Wurmus
2016-10-08  9:55     ` Danny Milosavljevic
2016-10-09 20:13   ` Security updates (was Re: texmaker, Qt and Chromium) Leo Famulari
2016-10-09 21:07     ` Kei Kebreau
2016-10-09 22:09       ` Leo Famulari
2016-10-09 21:33     ` Ludovic Courtès
2016-10-11 11:40     ` ng0
2016-10-08  9:12 ` texmaker, Qt and Chromium David Craven
2016-10-08  9:23   ` Ricardo Wurmus
2016-10-08 21:35     ` Roel Janssen
2016-10-08 21:46       ` Ricardo Wurmus
2016-10-10 10:41         ` Roel Janssen
2016-10-08 21:53       ` Danny Milosavljevic
2016-10-08 20:18 ` Efraim Flashner
2016-10-08 21:00   ` Ricardo Wurmus
2016-10-08 21:08     ` Efraim Flashner
2016-10-08 21:20       ` ng0 [this message]
2016-10-08 21:24       ` Danny Milosavljevic

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=87mvieillh.fsf@we.make.ritual.n0.is \
    --to=ngillmann@runbox.com \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).