On 2011-02-25 20:43:04 (+0100), Pascal Bleser <[email protected]> wrote: > Is there a specific reason why we build libcaca in our > repository ? (currently in Essentials) > > 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. > > Is it just because < 11.4 have older versions ? > 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) > > 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 :)).
Actually, I decided to go forward and disabled building libcaca in our repository for everything except Evergreen_11.1 and SLE_11 (which have really old versions in the distro, although even there, I wonder whether we shouldn't use the distro's version except if it makes the build fail for MPlayer etc..) Affected packages that depend on libcaca: MPlayer gstreamer010-plugins-good old-gstreamer010-plugins-good vlc xine-lib They all build just fine. If, again, you think we should use the latest libcaca as a dependency for those packages above, please let me know or re-enable it for that distribution version yourself. Please make sure it's a good reason though, let's avoid package upgrading side-effects on dependencies unless really needed. cheers -- -o) Pascal Bleser <[email protected]> /\\ http://opensuse.org -- I took the green pill _\_v FOSDEM XI: 5 + 6 Feb 2011, http://fosdem.org
pgpE5Tf2eiJhi.pgp
Description: PGP signature
_______________________________________________ Packman mailing list [email protected] http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
