[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: texmaker, Qt and Chromium
From: |
Roel Janssen |
Subject: |
Re: texmaker, Qt and Chromium |
Date: |
Sat, 08 Oct 2016 23:35:53 +0200 |
User-agent: |
mu4e 0.9.17; emacs 25.1.1 |
Ricardo Wurmus writes:
> David Craven <address@hidden> writes:
>
>>> What do you think? The alternative is to drop Texmaker and all the
>>> other packages that depend on Chromium as distributed by Qt.
>>
>> Weren't you vocal on IRC about bundling and the hell it brings? Sounds
>> like bundling is ok when it suits you... :)
>
> I have no problems dropping Texmaker. I’m not even using it.
Ouch. I was the one who submitted the package when the Qt modules
weren't unbundled yet (I guess). Now, because of a change of how we
package Qt, we're ready to remove a program that used to work just
fine..?
What's next? Throw the calibre package out of the window too because
it's broken for GNU Guix users?
Kind regards,
Roel Janssen
- Re: texmaker, Qt and Chromium, (continued)
- Re: texmaker, Qt and Chromium, Danny Milosavljevic, 2016/10/08
- Re: texmaker, Qt and Chromium, Ricardo Wurmus, 2016/10/08
- Security updates (was Re: texmaker, Qt and Chromium), Leo Famulari, 2016/10/09
- Re: Security updates (was Re: texmaker, Qt and Chromium), Ludovic Courtès, 2016/10/09
- Re: Security updates (was Re: texmaker, Qt and Chromium), ng0, 2016/10/11
- Re: texmaker, Qt and Chromium, David Craven, 2016/10/08
Re: texmaker, Qt and Chromium, Efraim Flashner, 2016/10/08