> 6 мая 2015 г., в 15:58, Alexander Shukaev <[email protected]> написал(а):
>
> On Wed, May 6, 2015 at 2:54 PM, Alexpux <[email protected]
> <mailto:[email protected]>> wrote:
>
>> 6 мая 2015 г., в 15:49, Alexander Shukaev <[email protected]
>> <mailto:[email protected]>> написал(а):
>>
>>
>>
>> On Wed, May 6, 2015 at 2:31 PM, David Macek <[email protected]
>> <mailto:[email protected]>> wrote:
>> On Thu, Apr 30, 2015 at 5:14 PM, Alexander Shukaev wrote:
>> > I've talked to Emacs devs, and it's still questionable whether they will
>> > backport that. It seems like releases of Emacs 24.x are going to be
>> > suspended.
>> >
>> > Another question though, is it possible to make an option to install
>> > "libgnutls-28.dll".
>>
>> You are of course free to downgrade/freeze your packages as you see fit, but
>> remember that it's not a supported scenario.
>>
>> > Emacs devs, for examples, also told me that the new GnuTLS has some
>> > security issues, and is generally not meant for broad public yet. It's
>> > good that MSYS2 is constistently catching up with bleeding edge features,
>> > but it's also not good to blindly switch to new libraries/tools without
>> > having an option to switch back. What do you think?
>>
>>
>> We're following the model of Arch Linux, and the phrase "to blindly switch
>> to new libraries" describes the model pretty well :). However, Arch Linux
>> _is_ doing some testing before releasing new versions and they're also on
>> v3.4.x, so maybe the issues are not so bad.
>>
>> Other than that, I can't say much about the GnuTLS upgrade or its
>> implications, that's Alexey's field.
>>
>> The point is not to change the default fact of upgrading to the newest
>> packages. The point is to add an option to install previous versions of
>> GnuTLS, while still having the latest one. I don't propose to do that for
>> all packages. Here is an exceptional case, where a library remains
>> compatible between very rare releases of new interface (26, 28, 30), so why
>> not allow an option to install all of them? For instance, `emacs-git'
>> (which will become Emacs 25 soon) already has a feature to switch between
>> those 3 versions of GnuTLS interface (only at compile time however). So how
>> about `gnutls-26', `gnutls-28', `gnutls-30' packages with `gnutls' pointing
>> at `gnutls-30'?
>>
>> On 6. 5. 2015 12:28, Alexander Shukaev wrote:
>> > I'm not a huge fan of bumping, but this is just to let you know that I'm
>> > still interested in your vision on this question.
>>
>> My vision is that GnuTLS is left as is, and Emacs can be fixed as I
>> described before:
>>
>> On 30. 4. 2015 17:01, David Macek wrote:
>> > 2) The fix can be cherry picked into a patch file and the mingw-w64-emacs
>> > package can be modified to apply the patch. If you make a correct pull
>> > request for this, I believe it will be accepted and the new,
>> > GnuTLS-enabled packages shall become available in the repositories soon.
>> > When a proper release comes out, the patch can be removed.
>>
>> Although it's a very small change(*) and I could do it, I was hoping you
>> would, because you're definitely more able to test the resulting build.
>>
>> *) Essentially this: export GnuTLS patch file from Emacs git history, put it
>> into mingw-w64-emacs directory, add to sources=, add line to prepare(),
>> increase pkgrel, update checksums, build, test, commit, push, send pull
>> request.
>>
>> There is no point of doing that anymore as 24.x series are suspended. As
>> for the question, I refereed only to having an option of installing
>> different GnuTLS interfaces.
>>
>
> I don’t want to maintain/build multiple versions of one package because I
> spent too much time on it. You can create local packages, for example,
> gnutls28 and build it yourself (also don’t forget to resolve issues with
> files conflict between different gunnels versions).
> Not only EMACS depends on Gnutls package, so you need be able to install
> multiple gnutls packages at the same time.
>
> Regards,
> Alexey.
>
>> Regards,
>> Alexander
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
>>
>> <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________>
>> Msys2-users mailing list
>> [email protected] <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/msys2-users
>> <https://lists.sourceforge.net/lists/listinfo/msys2-users>
>
> Yes, Alexey, I understand that. What if I will contribute that? Will this
> be accepted?
Sorry, no. We will have only one version of GNUTLS and EMACS.
As I told «I DON’T WANT TO BUILD IT» every time when one of gnutls dependency
was updated.
>
> Regards,
> Alexander
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
