Why does amarok depend on ASF/MP4 support?

[Andreas Pakulat]

On 29.09.09 23:46:11, Andreas Pakulat wrote:
> On 29.09.09 19:26:30, İşbaran Akçayır wrote:
> > Andreas Pakulat wrote On 29-09-2009 19:03:
> > > Hi,
> > >
> > > I've just had to update taglib to 1.6 for juk, just to find out that amarok
> > > doesn't build with a standard taglib as it checks for MP4/ASF support in
> > > taglib. Why is this not optional? I don't have any asf or mp4 files, why
> > > do I need to be bothered with that?
> > 
> > This was already answered in this mailing list, to summarize, reason for 
> > this is mostly to force packet maintainers in different distros to 
> > compile asf/mp4 with taglib, thus giving all amarok users the same 
> > amarok with same abilities.. its nothing that bad at all, you'll just 
> > have to pass two words to taglib configure options. ( -DWITH_ASF=On 
> > -DWITH_MP4=On )
> 
> Then why doesn't taglib enforce asf/mp4 support? If its supposed to be
> shipped with that, there's no reason to provide an option. Thats just
> useless bloat on the cmake files and confuses people that build from
> source and don't know in-depth all of the deps (And I only build taglib
> from source because 1.6 is not yet available here).

Heh, I should aptitude update more often, 1.6 is available in unstable
already.. Still I think taglib should just not make these options
available if apps using taglib need it.

Andreas

-- 
A gift of a flower will soon be made to you.