public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sébastien Fabbro" <bicatali@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [PATCH 00/10] alternatives-2.eclass updates
Date: Tue, 21 Jan 2014 14:46:30 -0800	[thread overview]
Message-ID: <CAA-OU2pBVAyog1bbtwrYPhkBc2SB2fSeGOD+LFZnU1Wo61nQ_Q@mail.gmail.com> (raw)
In-Reply-To: <20140121213017.GC13149@dhcppc1>

[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]

On Tue, Jan 21, 2014 at 1:30 PM, Reinis Danne <rei4dan@gmail.com> wrote:

>
>
> Ok, that is different issue. The question is whether we want,
> e.g., eselect blas be build time only or also runtime setting.
>
> If we use provider specific sonames, then the program will use
> whatever provider was selected at build time even if different
> provider is set afterwards. Thus it is build time only setting,
> with the caveat that package has to be rebuilt if selected
> provider is removed (preserved-libs should catch this).
>
> ⬑ This is how it is now in the overlay.
>

One other advantage of keeping the generic names is also that maintainer
would not have to modify the ebuild for packages to link with the selected
provider. Most blas dependent packages assume there is /usr/lib/libblas.so.

Some applications (I can see armadillo, scamp) actually use the
atlas-specific routines clapack_* routines.
We could aim at keeping both the library soname and filename as close to
upstream, and add an option to the alternative framework to create a
ldscript with a generic soname and filename, turned on for blas and cblas
at least.

As a user, I don't particularly enjoy rebuilding octave, ROOT, R, or the
scipy stack. @preserved-rebuild is more a hack than a feature.
I don't know how many people actually switch providers, besides a first
benchmark test. My guess is probably not many given the burden of
re-compiling all the reverse dependencies and the previous fragility of the
system.

Sebastien

[-- Attachment #2: Type: text/html, Size: 2125 bytes --]

  reply	other threads:[~2014-01-21 22:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 17:53 [gentoo-science] [PATCH 00/10] alternatives-2.eclass updates Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 01/10] alternatives-2.eclass: Update copyright Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 02/10] alternatives-2.eclass: Remove unused variables Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 03/10] alternatives-2.eclass: Move EXPORT_FUNCTIONS to top Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 04/10] alternatives-2.eclass: Remove commented-out code Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 05/10] alternatives-2.eclass: Put commonly used path in local variable Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 06/10] alternatives-2.eclass: Fix eclass name in comments Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 07/10] alternatives-2.eclass: Add EAPI check Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 08/10] alternatives-2.eclass: Add documentation comments Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 09/10] alternatives-2.eclass: Minor comment changes Reinis Danne
2014-01-20 17:53 ` [gentoo-science] [PATCH 10/10] alternatives-2.eclass: Use consistent quoting Reinis Danne
2014-01-21  6:51 ` [gentoo-science] [PATCH 00/10] alternatives-2.eclass updates justin
2014-01-21 18:32   ` Reinis Danne
2014-01-21 17:04 ` Sébastien Fabbro
2014-01-21 19:26   ` Reinis Danne
2014-01-21 20:04     ` Sébastien Fabbro
2014-01-21 20:35       ` François Bissey
2014-01-21 21:30       ` Reinis Danne
2014-01-21 22:46         ` Sébastien Fabbro [this message]
2014-01-22  7:13           ` justin
2014-01-21 21:21   ` justin
2014-01-21 21:26     ` François Bissey

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=CAA-OU2pBVAyog1bbtwrYPhkBc2SB2fSeGOD+LFZnU1Wo61nQ_Q@mail.gmail.com \
    --to=bicatali@gentoo.org \
    --cc=gentoo-science@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox