On Wed, Jan 22, 2014 at 10:54:48PM +1300, François Bissey wrote: > On 2014-01-22 22:47, Reinis Danne wrote: > > On Tue, Jan 21, 2014 at 07:47:48PM -0600, Steven Trogdon wrote: > >> On Wed, 22 Jan 2014 13:52:57 +1300 > >> François Bissey <[email protected]> wrote: > >> > >> > We have yet another instance of someone emerging lapack-reference > >> > without > >> > a valid blas configuration in > >> > https://bugs.gentoo.org/show_bug.cgi?id=498490 > >> > (not their original problem). > >> > I think we should do something about this in lapack-reference and > >> > possibly > >> > other ebuilds. > >> > In pkg_setup, we could run > >> > eselect blas update > >> > to make sure that a valid configuration is active > >> > and display an informational message about the blas provider > >> > used with the output of > >> > eselect blas show > >> > > >> > Who thinks is a good/bad idea? > >> > > >> > Francois > >> > > >> > >> For one, I'm in favor of something like this - though I probably don't > >> have > >> much say in the matter. I've been bitten by not eselecting {blas, > >> cblas, > >> lapack} after an upgrade. And I've even posted on this forum the > >> problem. > >> > >> http://article.gmane.org/gmane.linux.gentoo.science/1915 > >> http://article.gmane.org/gmane.linux.gentoo.science/1916 > >> > >> I resolved things, quite accidently, by re-eselecting the important > >> components which were eselected before the upgrade. > >> > >> Steve > >> > > > > I fixed provider selection during upgrades in overlay > > (yesterday). Now it should have valid provider set at any time. > > With that do you still think it would need this extra eselect > > update in ebuild? > > > > > It seems that the difficult point is when you go from no provider > available > to one provider available. If that case is fixed then: No
That case also works. Reinis
