Re: Why is redhat-artwork multi-lib?

[seth vidal <skvidal linux duke edu>]

On Mon, 2007-02-12 at 10:03 -0500, Matthias Clasen wrote:
> Michael Schwendt wrote:
> > In the rawhide for x86_64 repository:
> >
> >   redhat-artwork - 5.0.8-4.fc7.i386
> >   redhat-artwork - 5.0.8-4.fc7.x86_64
> >
> > $ rpm -q --provides redhat-artwork
> > bluecurve.so  
> > config(redhat-artwork) = 5.0.8-1.fc6
> > kwin3_bluecurve.so.0  
> > libbluecurve.so  
> > redhat-artwork = 5.0.8-1.fc6
> >
> > $ rpm -ql redhat-artwork|wc -l
> > 8045
> > $ rpm -ql redhat-artwork|grep share|wc -l
> > 8024
> >
> > Why is such a huge data (!) package, which contains over 8000 files in
> > /usr/share, merged with the few arch-specific bluecurve libs, so that it
> > becomes a multi-lib package?
> >
> >   
> History.
> Thats just the way it was initially done, before multilib became an issue.

okay, But now that multilib is an issue is it possible to un-do this so
it can be a nice noarch pkg?

-sv