Bug 229450 - Cannot Add Package through Project Properties
Cannot Add Package through Project Properties
Product: Fedora
Classification: Fedora
Component: anjuta (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Debarshi Ray
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-02-21 02:29 EST by mrjianpu
Modified: 2008-04-12 08:58 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-12 08:58:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description mrjianpu 2007-02-21 02:29:17 EST
Description of problem:
If there is no package specified in the "configure.in.tpl" file, user cannot add
package through the Project Properties Packages page after creating a project.

Version-Release number of selected component (if applicable):
Anjuta 2.0.2

How reproducible:

Steps to Reproduce:
1.  Create a C++ console project as usual.
2.  Click Project->Properties->Packages (now the input box is empty).
3.  Click Add Module to add a name, say PACKAGE; then select it.
4.  Click Add Package to add a package, say glibmm-2.4.
5.  Click Close.
6.  Click Build->Run Autogenerate->Ok
7.  Click Build->Build Project

Actual results:
Neither compile nor link options are added during the compile and link
processes.  An inspection of the "configure.in" file shows: 


The value "glibmm-2.4" is not properly quoted. and both the

Expected results:
After the packge is added, the "configure.in" file should contain:

Comment 1 Debarshi Ray 2008-03-01 09:11:02 EST
Reassigning to myself because I own this package now.
Comment 2 Bug Zapper 2008-04-04 02:19:24 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Debarshi Ray 2008-04-11 01:11:31 EDT
I am looking into this.
Comment 4 Debarshi Ray 2008-04-12 08:58:15 EDT
With Anjuta 2.2.3 I got the following in configure.ac: (I used glib instead of

Both "Build->Run Autogenerate->Ok" and "Build->Build Project" completed

Please feel free to reopen this if the problem persists.

Note You need to log in before you can comment on or make changes to this bug.