Atlas proposal

Josselin Mouette joss at
Tue Aug 17 22:42:06 UTC 2010

Le mardi 17 août 2010 à 23:09 +0200, Sylvestre Ledru a écrit :
> After some discussions at the DebConf, here is a proposal on what should
> be done:
> * drop all optimized packages from the archive
> * only provide libatlas3gf-base & libatlas-base-dev without any
> extension and limited to one thread.
> * Update the description of the package with these information.
> * During the installation of the package, through debconf, inform the
> user that the current package is under optimized and better performances
> would be achieved by recompiling locally the package (which takes time
> anyway)
> * Through the DebConf process, propose to the user to build and install
> the optimized package

This sounds like debconf abuse.

Just ship two packages: libatlas3gf-base and libatlas3gf-auto, with
appropriate Conflicts/Provides just as we have now. And have
libatlas3gf-auto depend on all build-dependencies, ship the source, and
build itself in its postinst. Gentoo-style.

In libatlas3gf-auto you could use debconf for overriding things like the
number of threads or some optimizations, but I wouldn’t use debconf for
selecting the implementation.

 .''`.      Josselin Mouette
: :' :
`. `'  “If you behave this way because you are blackmailed by someone,
  `-    […] I will see what I can do for you.”  -- Jörg Schilling
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the debian-science-maintainers mailing list