unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rodger Fox <thylakoid@openmailbox.org>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add lmms
Date: Thu, 16 Mar 2017 22:54:09 -0700	[thread overview]
Message-ID: <635cca1faad75c7c087346622f9b46c2@openmailbox.org> (raw)
In-Reply-To: <20170315220333.GA20748@jasmine>

> Qt 4 is no longer supported by the Qt project, but security
> vulnerabilities continue to be discovered in it, and so we should not
> add new packages that depend on it.
> 
> Apparently, LMMS can be built with Qt 5:
> 
> https://github.com/LMMS/lmms/wiki/Compiling-lmms#using-qt5
> 
> Can you try it and let us know how it goes?

Ok, I looked into this. Qt5 is supported only in the newest development
version of lmms, but what I packaged is the latest stable release.

I will make a note of this for when I update the package, but what can
we do for the mean time? Accept this as is? Package the release
candidiate? Or just wait for the next stable release of lmms before
adding this to guix?

To be honest, the RC looks like it has some cool new features, so I
will probably be building it for myself either way. Also, lmms is on
a pretty slow release cycle. The last stable was 2015, RC-1 was
early 2016, and RC-2 was Jan 2017. So maybe if it seems stable enough
when I build it I can package the RC-2. I could do one for each if that
makes sense, kind of like the guile and guile-next packages.
What do you think? lmms and lmms-rc?

-Rodger

  reply	other threads:[~2017-03-17  5:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09  4:47 [PATCH] gnu: Add lmms Rodger Fox
2017-03-15 22:03 ` Leo Famulari
2017-03-17  5:54   ` Rodger Fox [this message]
2017-03-21 19:20     ` Leo Famulari
2017-03-21 19:39 ` Leo Famulari
  -- strict thread matches above, loose matches on Subject: below --
2017-02-23 18:13 Rodger Fox
2017-02-24 10:56 ` Julien Lepiller
     [not found] <mailman.54228.1487857637.22740.guix-devel@gnu.org>
2017-02-23 16:38 ` Rodger Fox
2017-02-22 23:18 Rodger Fox
2017-02-23  9:15 ` julien lepiller
2017-02-23 11:30   ` ng0

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=635cca1faad75c7c087346622f9b46c2@openmailbox.org \
    --to=thylakoid@openmailbox.org \
    --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 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).