[packman] Why do we build libcaca ?

Manfred Tremmel manfred at links2linux.de
Fri Feb 25 21:29:57 CET 2011

Am Freitag, 25. Februar 2011 schrieb Pascal Bleser:
> Is there a specific reason why we build libcaca in our
> repository ? (currently in Essentials)

I've added it at a time libcaca got incompatible from one version to 
another and some packages (as xine-lib) needed a version which was up to 
date. I don't remember when it was, but beta14 is at the moment what's 
minimum required in the xine-lib configure script. So the openSUSE 11.1 
package is to old.

> We build 0.99.beta17
> 11.4 has 0.99.beta17
> 11.3 has 0.99.beta16
> 11.2 has 0.99.beta16
> 11.1 has 0.99.beta13b
> There is no "special" dependency in it, so there is no
> "uncrippling" reason to build it ourselves.

No, it's a "non critical package".

> Is it just because < 11.4 have older versions ?

It' was necessary for openSUSE <= 11.1 and has beend enabled also for 
openSUSE >= 11.2 when it was updated.

> If so, wouldn't it be okay to build against 0.99.beta16 on 11.3
> and 11.2 ? (rather than introducing an upgrade side-effect in
> Essentials)

Would be possible.

> Please let me know if there is a good reason of having the
> latest in our repository (other than the above, in which case I
> will only build libcaca for 11.1 and SLE_11 :)).

If adding the package to our repository why not building for all SUSE 
versions? It's not easy to explain why openSUSE 11.1 users will get 
0.99.beta17 and openSUSE 11.2 and 11.3 users should use 0.99.beta16. And 
it doesn't make bug hunting easier to take care of the different bugs in 
the different versions.

Machs gut    | http://www.iivs.de/schwinde/buerger/tremmel/

Manfred      | http://packman.links2linux.de/

More information about the Packman mailing list