From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 27546@debbugs.gnu.org
Subject: [bug#27546] [PATCH] Add wine stable release
Date: Sun, 02 Jul 2017 17:09:04 +0200 [thread overview]
Message-ID: <87o9t27u5r.fsf@gnu.org> (raw)
In-Reply-To: <20170702114212.GA30356@jasmine.lan> (Leo Famulari's message of "Sun, 2 Jul 2017 07:42:12 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sat, Jul 01, 2017 at 09:41:37PM +0200, Nicolas Goaziou wrote:
>> > Since we don't typically package development releases, how about
>> > removing 2.11 and replacing it with 2.0.1?
>>
>> Thank you for the review.
>>
>> I do not mind, for all I need is the stable release. However, I'm not
>> the one who packaged wine in the first place. Maybe its author has
>> a different use case.
>
> I see.
>
>> Anyway, the patch implements the less invasive solution. We can also
>> apply it for now and settle on the next stable release, whenever it
>> happens. Note that we have other packages in the same situation (e.g.,
>> lilypond).
>
> IIUC, I think that's a good idea. We'll keep both versions of Wine until
> the development releases reach "stable" status, then we'll drop the
> development version.
Sounds reasonable to me too.
As for the name, I would call the stable version “wine”, and the
development version “wine-next” (we’ve used this naming scheme on a few
occasions for other packages in the past.) That way users won’t get the
development version unless they explicitly ask for it.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-07-02 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 11:53 [bug#27546] [PATCH] Add wine stable release Nicolas Goaziou
2017-07-01 17:38 ` Leo Famulari
2017-07-01 19:41 ` Nicolas Goaziou
2017-07-02 11:42 ` Leo Famulari
2017-07-02 15:09 ` Ludovic Courtès [this message]
2017-07-02 21:25 ` Nicolas Goaziou
2017-07-03 7:33 ` Ludovic Courtès
2017-07-03 16:19 ` Nicolas Goaziou
2017-07-18 12:44 ` bug#27546: " Alex Kost
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=87o9t27u5r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27546@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.