Re: [Plplot-devel] PLplot statistics

[<jca...@in...>]

On Friday 08 February 2002 06:38, Alan W. Irwin wrote:
| On Fri, 8 Feb 2002, [iso-8859-1] Jo=E3o Cardoso wrote:
| > On Thursday 07 February 2002 22:30, Alan W. Irwin wrote:
=2E..
| > But I don't see the point in installing rpms under /usr -- there
| > must exist some reasoning behind that?
|
| It's traditional. Maybe its even in the LSB by now, but violate
| that tradition at your peril.

OK, but tradition is not the same as it was to be :)

| > I have yet another rpm question. With dyndrivers, we can make rpm
| > with all available drivers, without having to worry if the user
| > system has the necessary libs or not! Of course the user will not
| > be able to use those drivers, but it will not hurt, and if the
| > user latter install the extra packages the drivers will be there.
| > Correct?
|
| Didn't we just go through this exercise to prove the libraries had
| to be there (i.e., mentioned specifically for the link command) for
| the dynamic driver builds?

I don't quite understand your phrasing. libplplot only depends on the=20
libs the xwin and tk drivers depend on, if they are build. Building=20
dynamic drivers does not put dependencies in libplplot and in none of=20
the executables, so I can build all dyn-drivers I can and package=20
them. If "rpm" creates dependencies on the package, then one has to=20
find the way to manually remove them (at rpm creation time).

| Anyhow, when building from a src rpm we use the ordinary configure
| script just like when building from a tarball or cvs. (And I am
| sure Rafael would answer the same for the deb package build.) Our
| current configuration checks for certain libraries and headers on
| the build machine.  If libcd is not there it doesn't build the cgm
| driver.  If libgd isn't there, it doesn't build the gd driver with
| png and jpeg devices.  This is uniform across src rpm, (presumably)

I know all that, I just wanted to stress the fact that one can=20
distribute drivers even knowing that the user system might not have=20
imediate support for some of them.

I don't agree with Rafael idea of creating a separate rpm for each=20
driver!
What a mess to install all those perl modules! That's good only for=20
debian, and for guys who know what they are doing. When I installed =20
those perl modules I was tempted to (and just did)  install them all,=20
because their names tell me nothing.

| If you run into any specific problems with a src rpm build of say
| PLplot, don't hesitate to ask me for help.  But my help will only
| be effective if the system has been cleanly installed strictly from
| rpm's without any forcing.

As you might have understand, I start creating a rpm for suse, but my=20
system is far from clean. I do know however what I have installed by=20
hand, from suse packages, or from other disto packages.

Joao