Clearly, the best thing to do is simply to ask people to install the jpeg
rpm first. 99.9999% of people will have it or can trivially install it.
JPEG was historically not availalbe by default on alpha and sun.
The RPM build can still have dependencies on JPEG even if the JPEG rpm
itself does not build. One of the problems is that "jpeg" is a dependency
on other packages (and they should still depend on the "jpeg" rpm being
available).
It would be entirely possible to dump JPEG from the thirdparty directory
and simply say it's a dependency that most people have. We don't really
want to get into the game of making rpm packages for packages that already
have perfectly good rpm packages. [tcl/tk springs to mind but ccdpack is
killing us here]
Tim
On Fri, 20 May 2005, Norman Gray wrote:
> Steve,
>
> On 2005 May 19 , at 19.24, Rankin, SE (Stephen) wrote:
>
>> The JPEG build only builds on a system if configure does not find it
>> already on the system.
>
> Indeed, and I worked hard to get it that way!
>
>> Is there any way of overriding this and build it
>> anyway?
>>
>> On RHEL x86_64 JPEG does not get built in the nightly build for this
>> reason.
>
> It doesn't build if it's determined that it doesn't need to be built,
> because it's already available on the system. If it's already
> available, there's surely no need to check that our unnecessary build
> works.
>
> See you,
>
> Norman
>
>
> --
> ----------------------------------------------------------------------
> Norman Gray : Physics & Astronomy, Glasgow University, UK
> http://www.astro.gla.ac.uk/users/norman/ : www.starlink.ac.uk
>
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|