On Sáb 10 Sep 2011 17:32:30 Anton Gladky escribió: > I propose to remove paraview-dev at all and include all files into the > paraview-binary, like it was in previous versions of paraview.
That sounds like a very bad decision. Header files should be provided by the
-dev package.
This allows a user to get only the binaries when she installs the foo package
(foo being paraview in this case) and the header files only when necessary. If
the header files are provided by the same package, it means that the buildd
(or anyone wanting to B-D on paraview) must install a lot of unused stuff.
Now ParaViewConfig.cmake should be installed by paraview-dev. To help the
transition, all the packages that currently build-depend on paraview should be
filled a normal bug, raised to important in ~3 or 4 weeks and then to serious
~3 or 4 weeks later. It is customary to user-tag the bugs so as to follow the
transition.
After that is achieved, src:paraview can be uploaded with the dev package
providing the header files and ParaViewConfig.cmake.
Kinds regards, Lisandro.
--
6: Cual es el boton del mouse que permite acceder a las acciones mas
comunes del manejo de archivos
* Depende el tipo de accion mas comun
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
