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 319725 - The pkgconfig module changes with each stable version
The pkgconfig module changes with each stable version
Status: VERIFIED INVALID
Product: gedit-plugins
Classification: Other
Component: General
unspecified
Other All
: Normal minor
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2005-10-25 12:11 UTC by Alexey Rusakov
Modified: 2019-03-23 20:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Alexey Rusakov 2005-10-25 12:11:03 UTC 
Please describe the problem:
As far as I know, there are gedit-2.6.pc, gedit-2.8.pc, gedit-2.10.pc, and
gedit-2.12.pc files, one for each of stable gedit versions. This makes
troublesome to maintain external plugins for gedit (such as, say, Seahorse
plugin), since I have to track the ever-changing version of pkgconfig module.
From the other hand, Seahorse plugin that was last compiled against gedit-2.10,
compiled without problems with a new gedit-2.12 as well - but I had to alter
configure.ac explicitly for this.
Is there a serious reason to change pkgconfig module with each stable version?

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Paolo Borelli 2005-12-15 20:48:26 UTC 
(sorry for having never given signs of life in this bugreport)


I guess that part of the reason is that the plugin api was not offering enough
guaranties of stability (ok, in reality it changed very little over time, but
this was more due to lack of work on it that on api stability guaranties :).


In 2.13.0 we changed the api radically, this time for good so we will bump it to
the .pc file to 2.14... maybe if all goes well we can keep it stable in the
following versions.
Comment 2 Alexey Rusakov 2008-02-10 17:03:40 UTC 
I believe it's best to close this as INVALID, because .pc files changed according to API changes.