[bug-notifications] [qt4_dev 0005075]: Qt packaging doesn't respect our file system layout standard

[Mantis Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=5075 
====================================================================== 
Reported By:                pfelecan
Assigned To:                cgrzemba
====================================================================== 
Project:                    qt4_dev
Issue ID:                   5075
Category:                   
Reproducibility:            always
Severity:                   tweak
Priority:                   high
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2013-05-11 10:31 CEST
Last Modified:              2013-09-29 09:19 CEST
====================================================================== 
Summary:                    Qt packaging doesn't respect our file system layout
standard
Description: 
The package installs a lot of directories directly in the root of Open CSW
tree, /opt/csw, e.g. prototypes, mkspecs, &c.

This rises errors in checkpkg, e.g. when a dynamic shared object is
installed in /opt/csw/prototypes it is flagged with the
"binary-architecture-does-not-match-placement" tag.

After having discussed the issue on the "devel" mailing list,
http://lists.opencsw.org/pipermail/devel/2013-May/026324.html, I propose to
modify the recipe in order to install the various component in appropriate
directories. For this, you can use inspiration given by Debian's packaging,
http://packages.debian.org/wheezy/i386/python-qt4/filelist
====================================================================== 

---------------------------------------------------------------------- 
 (0010586) pfelecan (manager) - 2013-09-29 09:19
 https://www.opencsw.org/mantis/view.php?id=5075#c10586 
---------------------------------------------------------------------- 
the last releases have fixed this.