public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: "François Bissey" <f.r.bissey@massey.ac.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sage-4.3.5-r1 && sage-core
Date: Mon, 19 Apr 2010 22:36:01 +1200	[thread overview]
Message-ID: <201004192236.01946.f.r.bissey@massey.ac.nz> (raw)
In-Reply-To: <201004192113.02032.f.r.bissey@massey.ac.nz>

> > In my opinion, the best "solution" would be to print out a warning/info
> > after  installing sage-core which basically says revdep-rebuild reports
> > false positives and just wait for the Sage people upgrading to a new
> > release of Singular (see http://trac.sagemath.org/sage_trac/ticket/8059
> > and
> > http://trac.sagemath.org/sage_trac/ticket/8228).
> 
> Hi Christopher,
> 
> A warning is good but I would prefer to to put the libraries linking
> to libsingular in quarantine for revdep-rebuild until that happens.
> Otherwise revdep-rebuild will always want to rebuild sage-core again
> and again. Furthermore:
> 1) we cannot count on users reading the warning.
> 2) during any genuine call to revdep-rebuild to catch other stuff
> sage-core will be added and considering the time it takes it is
> not nice.
> 
I did go ahead and added a revdep-rebuild exception file.
The problem has completely disappeared now.

Francois



  reply	other threads:[~2010-04-19 11:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18  9:02 [gentoo-science] sage-4.3.5-r1 && sage-core Christopher Schwan
2010-04-18 19:10 ` Steven Trogdon
2010-04-18 20:28   ` Christopher Schwan
2010-04-19  3:18     ` François Bissey
2010-04-19  8:52       ` Christopher Schwan
2010-04-19  9:13         ` François Bissey
2010-04-19 10:36           ` François Bissey [this message]
2010-04-19 11:04             ` Christopher Schwan
  -- strict thread matches above, loose matches on Subject: below --
2010-04-18  5:32 Steven Trogdon
2010-04-18  7:46 ` François Bissey
2010-04-18  7:51 ` François Bissey
2010-04-18  7:58 ` François Bissey
2010-04-18  8:04 ` Christopher Schwan

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=201004192236.01946.f.r.bissey@massey.ac.nz \
    --to=f.r.bissey@massey.ac.nz \
    --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