After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 632964 - Jhbuild should suggest to remove .la files
Jhbuild should suggest to remove .la files
Status: RESOLVED WONTFIX
Product: jhbuild
Classification: Infrastructure
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Jhbuild maintainers
Jhbuild QA
Depends on:
Blocks:
 
 
Reported: 2010-10-23 10:33 UTC by Olav Vitters
Modified: 2011-09-01 06:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Olav Vitters 2010-10-23 10:33:50 UTC 
Some distributions still leave .la files everywhere.

The GnomeShell wiki page recommends people to remove these files:
http://live.gnome.org/GnomeShell/RemovingLaFiles

There are instructions for .dpg based systems. I've added instructions for (new) .rpm based systems as well. Though Fedora+RHEL do not need such instructions.

Perhaps jhbuild should check for the existance of .la and warn against it?
Comment 1 Craig Keogh 2011-06-22 23:57:00 UTC 
Sorry for the mark duplicate of newer bug. Removing la files is now implemented in JHBuild.

*** This bug has been marked as a duplicate of bug 647231 ***
Comment 2 Olav Vitters 2011-06-23 18:51:50 UTC 
That bug is really nice, but not what I meant. I meant that jhbuild warns when there are system installed .la files (/usr/*). Maybe that is too much, in which case this should be wontfixed.
Comment 3 Craig Keogh 2011-06-24 00:05:46 UTC 
If JHBuild suggests the user delete /usr/lib/libblah.la, the distro package manager would resurrect the file. The solution would be to file a bug with the distro not to distribute the .la file. I'm don't think JHBuild should suggest filing bugs though.
Comment 4 Craig Keogh 2011-09-01 06:59:27 UTC 
This bug is addressed by my comment 3. If not happy, please reopen bug and lets discuss.