Le mercredi 30 mars 2016 à 22:03 +0200, Wolfgang Fütterer a écrit : > IMHO there are the following options to continue: > > 1) Removing suitesparse-metis from unstable > > I really don't know, weather this is a good idea or a really bad one. > > 2) Uploading a new version of suitesparse[2] build against metis and > replacing > suitesparse-metis. > > This would affect primarily two libraries in suitesparse (libcholmod > and > libspqr). And could cause suitesparse move to contrib. (IMHO not > preferable) > > 3) copying the current source of suitesparse to suitesparse-metis > and > preparing a new version of suitesparse-metis with metis enabled. > > The latter corresponds to the current state. > > Any ideas anyone? Which of these options is preferable, if any? For me, 2) is clearly not an option, because I want suitesparse to stay in main. So either 1) and 3). I'm personally indifferent between the two, because I'm not interested in non-free software. Cheers, -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594
Attachment:
signature.asc
Description: This is a digitally signed message part