Hello, as i found out, this localization file location is not limited to scribus in its both variations, but also holds true for various other qt based packages. Among these are for example the packages for hydrogen, virtualbox*, qt4, skype, pdfedit, qdacco, mscore, djvu, canorus, calibre, avidemux, googleearth, and maybe lots others i am not aware of myself.
Instead of burdening localepurge with tracking such non-standard localization files, it would be advisable to have the affected packages fix the location of these translation files. In the long run this would be a cleaner solution. Other than that, dpkg already includes a feature to exclude specific files from any deb package from installation, rendering localepurge itself rather pointless these days. There is a nice article about this dpkg feature which is mentioned in wishlist bug #603587 and can be found at www.raphaelhertzog.com/2010/11/15/save-disk-space-by-excluding-useless-files-with-dpkg In fact, localepurge should be considered obsolete now, and it would be great if it could be replaced by some configuration frontend for the above mentioned dpkg exclude/include feature. Thanks Paul On 01/16/2011 11:21 AM, T(A)ILS developers wrote: > Package: localepurge > Version: 0.6.2+nmu1 > Severity: normal > > The scribus layout program stores its translation files under > /usr/share/scribus/translations. On my system they add up to 25M. I > would expect them to be cleaned when using localepurge. The same problem > exists with the scribus-ng package. > > I wonder whether this should be taken care of by localepurge or rather > corrected in scribus/scribus-ng. > > I don't mind sending you a patch for localepurge if you think this is > the right way to proceed. > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
