1 |
On Monday 19 April 2010 12:36:01 François Bissey wrote: |
2 |
> > > In my opinion, the best "solution" would be to print out a warning/info |
3 |
> > > after installing sage-core which basically says revdep-rebuild reports |
4 |
> > > false positives and just wait for the Sage people upgrading to a new |
5 |
> > > release of Singular (see http://trac.sagemath.org/sage_trac/ticket/8059 |
6 |
> > > and |
7 |
> > > http://trac.sagemath.org/sage_trac/ticket/8228). |
8 |
> > |
9 |
> > Hi Christopher, |
10 |
> > |
11 |
> > A warning is good but I would prefer to to put the libraries linking |
12 |
> > to libsingular in quarantine for revdep-rebuild until that happens. |
13 |
> > Otherwise revdep-rebuild will always want to rebuild sage-core again |
14 |
> > and again. Furthermore: |
15 |
> > 1) we cannot count on users reading the warning. |
16 |
> > 2) during any genuine call to revdep-rebuild to catch other stuff |
17 |
> > sage-core will be added and considering the time it takes it is |
18 |
> > not nice. |
19 |
> |
20 |
> I did go ahead and added a revdep-rebuild exception file. |
21 |
> The problem has completely disappeared now. |
22 |
> |
23 |
> Francois |
24 |
|
25 |
Ok, fine ! |
26 |
|
27 |
Christopher |