libgcrypt soname bump in rawhide

[Tomasz Torcz]

On Wed, Jul 02, 2014 at 06:03:33PM +0200, Kalev Lember wrote:
> On 07/02/2014 05:24 PM, Stephen Gallagher wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On 07/02/2014 11:22 AM, Stephen Gallagher wrote:
> >> On 07/02/2014 11:19 AM, Kalev Lember wrote:
> >>> On 07/02/2014 05:13 PM, Stephen Gallagher wrote:
> >>>> This is not an official solution, but I am now providing a
> >>>> COPR for Rawhide installs that provides a compatibility library
> >>>> for libgcrypt.
> >>
> >>> That's awesome, but can we get this in rawhide proper instead?
> >>> I'd be happy to help get this through the review process if you
> >>> need a reviewer.
> >>
> >>
> >> Short answer: no. I don't have the time or inclination to attempt
> >> to maintain a compat *crypto* library. There's far too much
> >> possibility for disaster there.
> 
> Fair enough, that's totally understandable if you don't want to maintain
> a crypto library. I just had to ask :)
> 
> However, we've got a F21 release looming closer and I'd like to make
> sure major 3rd party apps keep working out of the box. And yes, this
> includes Chrome.
> 
> This is especially important since we don't have Chromium in the Fedora
> repositories; otherwise we could tell users to use that instead.

  In this specific case, users have two options:
– use Chromium from Spot's repository
– use Chromium from Russian Fedora repository

  Third option is:
– use compat libgcrypt from Stephen's repository.

  Those are not really different, but I suppose maintaining multiple
version of crypto library is worse.  Either way, it is up to Google
to provide precompiled software with up-to-date environment.

-- 
Tomasz Torcz       ,,(...) today's high-end is tomorrow's embedded processor.''
xmpp: zdzichubg at chrome.pl                      -- Mitchell Blank on LKML