From: Kei Kebreau <kei@openmailbox.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add qscintilla.
Date: Mon, 19 Sep 2016 09:18:45 -0400 [thread overview]
Message-ID: <8760psjadm.fsf@openmailbox.org> (raw)
In-Reply-To: <20160918210202.GA853@macbook42.flashner.co.il> (Efraim Flashner's message of "Mon, 19 Sep 2016 00:02:02 +0300")
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
Efraim Flashner <efraim@flashner.co.il> writes:
> On Sun, Sep 18, 2016 at 04:56:34PM -0400, Leo Famulari wrote:
>> On Sun, Sep 18, 2016 at 04:10:15PM -0400, Kei Kebreau wrote:
>> > Andreas Enge <andreas@enge.fr> writes:
>> > > On Tue, Sep 13, 2016 at 04:37:35PM -0400, Kei Kebreau wrote:
>> > >> In this case, should I leave qtscintilla-qt4 as a public
>> > >> package in qt.scm
>> > >> instead of maths.scm as Leo suggested?
>> > >
>> > > since it is used for only one package and relies on the deprecated qt@4,
>> > > I would leave it private, regardless its name.
>> >
>> > It seems that there are conflicting opinions here. :)
>> > If no one minds, I can support this feature out-of-tree until GNU Octave
>> > updates its UI to use Qt 5.
>> >
>> > Opinions?
>>
>> I don't think we need to keep it out of tree.
>>
>> I agree with Andreas that we should discourage use of Qt 4, but I don't
>> think we should not use it at all, or else I would have suggested
>> removing all Qt 4 related software.
>>
>> I think that if there is a reason to export the package at this time, we
>> should do so. Otherwise, I think we should keep it private. If we need
>> to export it later, we can.
>>
>> Efraim, do you have a use for a Qt 4 variant of qscintilla?
>
> Nope.
To get this right: qscintilla will be defined publicly in qt.scm,
qscintilla-qt4 will be defined privately in maths.scm (how do I inherit
a package from another module?), and Octave will include qscintilla-qt4
and qt-4 as inputs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-09-19 13:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 17:31 [PATCH] gnu: Add qscintilla Kei Kebreau
2016-09-13 14:37 ` Kei Kebreau
2016-09-13 17:05 ` Leo Famulari
2016-09-13 18:01 ` Kei Kebreau
2016-09-13 18:14 ` Leo Famulari
2016-09-13 18:59 ` Kei Kebreau
2016-09-13 19:04 ` Leo Famulari
2016-09-13 19:40 ` Kei Kebreau
2016-09-13 19:39 ` Efraim Flashner
2016-09-13 20:37 ` Kei Kebreau
2016-09-13 20:48 ` Efraim Flashner
2016-09-14 17:08 ` Leo Famulari
2016-09-14 18:11 ` Kei Kebreau
2016-09-14 18:56 ` Leo Famulari
2016-09-14 20:37 ` Kei Kebreau
2016-09-14 20:42 ` Efraim Flashner
2016-09-15 14:20 ` Kei Kebreau
2016-09-15 14:25 ` Kei Kebreau
2016-09-18 8:36 ` Andreas Enge
2016-09-18 20:10 ` Kei Kebreau
2016-09-18 20:56 ` Leo Famulari
2016-09-18 21:02 ` Efraim Flashner
2016-09-19 13:18 ` Kei Kebreau [this message]
2016-09-19 13:25 ` Ricardo Wurmus
2016-09-19 14:47 ` Kei Kebreau
2016-09-19 21:32 ` Leo Famulari
2016-09-19 21:45 ` Kei Kebreau
2016-09-19 23:52 ` Leo Famulari
2016-09-22 19:02 ` Ricardo Wurmus
2016-09-24 3:30 ` Leo Famulari
2016-09-24 5:13 ` Kei Kebreau
2016-09-25 17:05 ` Leo Famulari
2016-09-25 19:25 ` Kei Kebreau
2016-10-03 16:17 ` Ludovic Courtès
2016-09-19 13:30 ` Andreas Enge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760psjadm.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.