[packman] Why do we build libcaca ?

Manfred Tremmel manfred at links2linux.de
Sat Feb 26 02:31:02 CET 2011


Am Samstag, 26. Februar 2011 schrieb todd rme:
> On Fri, Feb 25, 2011 at 5:54 PM, Manfred Tremmel 
<manfred at links2linux.de> wrote:
> > Am Freitag, 25. Februar 2011 schrieb Pascal Bleser:
> >> On 2011-02-25 22:17:47 (+0100), Manfred Tremmel
> >
> > <manfred at links2linux.de> wrote:
> >> > I think 99% of the users will never use a videoplayer with caca-
> >> > textoutput on console. For myselve I've done it a view times for
> >> > testing, but for nothing else. It's not realy usefull. So it's
> >> > completely unimportend even if we would build the mediaplayers
> >> > on opneSUSE 11.1 and SLES without caca.
> >>
> >> Hmmmmmmm... that's very true actually...
> >> So, would you be fine if I disable building libcaca for 11.1 and
> >> SLE_11 as well ? (and build MPlayer, vlc, ... without libcaca
> >> support on those)
> >
> > I wouldn't do this. This would cause a lot of spec-file changes.
> >
> > --
> > Machs gut    | http://www.iivs.de/schwinde/buerger/tremmel/
> >
> > Manfred      | http://packman.links2linux.de/
> 
> How many packages depend on this?  It is just 3 lines that can be
> copied and pasted between each spec file that has a direct
> buildrequires.  Unless there are a ton of packages that explicitly
> depend on this it wouldn't be that hard.

It's not as simple. It's not only a "%if %suse_version >= 1120" and 
"%endif" to put arround the "BuildRequires:  libcaca-devel". There are 
filelists to change and package descriptions (like in xine-lib). I think 
this is a waist of the limited time we have. And all this for a package 
(libcaca) we do have for a long time on the server and we know it makes 
no problem on a openSUSE 11.1.

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

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




More information about the Packman mailing list