#18899 closed defect (invalid)
py25-cairo-1.8.2 installs pkg-config file in wrong location
Reported by: | blb@… | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.0 |
Keywords: | pkg-config | Cc: | |
Port: | py25-cairo |
Description
python/py25-cairo on my system installs its pkg-config file within the python25 framework location:
${prefix}/Library/Frameworks/Python.framework/Versions/2.5/lib/pkgconfig/pycairo.pc
I haven't had a chance to find out why as yet, but that should be ${prefix}/lib/pkgconfig/pycairo.pc
.
Change History (8)
comment:1 Changed 16 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
comment:2 follow-up: 3 Changed 16 years ago by blb@…
Ah, yeah, that makes sense since it is an unversioned file...I just happened to notice it since my tab-completion stalled on that directory which I expected to only have python25 in it...
Anyway, I guess adding to pkg_config_path does make sense; should we document that someplace?
comment:3 Changed 16 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Status: | new → assigned |
---|
Replying to blb@…:
Anyway, I guess adding to pkg_config_path does make sense; should we document that someplace?
There are short comments in py-cairo and py25-cairo (but not py26-cairo), but I suppose a ui_msg in all of them might be in order.
comment:4 follow-up: 5 Changed 16 years ago by blb@…
Actually I was thinking more generally, as we'll probably find other modules which need the same change to where the .pc file goes. Though i'm unsure if it really fits into the port group docs or someplace else...
comment:5 Changed 16 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Replying to blb@…:
Actually I was thinking more generally, as we'll probably find other modules which need the same change to where the .pc file goes. Though i'm unsure if it really fits into the port group docs or someplace else...
Since python has its own category directory for all the pyXX- packages, then it does not unreasonable for it to have its own Wiki page.
I created a bare outline to be put up at http://trac.macports.org/wiki/Python.
Is it bad form to simply put up a new Wiki page without discussing it on the mailing list first?
comment:6 Changed 16 years ago by blb@…
Wiki page makes sense for now since I'm not sure quite where it would go in the guide as yet, and since the wiki is the preferred location for new stuff like that until integrated into the guide/man pages.
comment:7 Changed 16 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
http://trac.macports.org/wiki/Python has been created.
It is quite sparse at the moment, but I will try to improve it as time goes on.
The reason was was to avoid conflict with py-cairo, py26-cairo, and (probably eventually) py30-cairo.
For Portfiles, the idea was to set configure.pkg_config_path to ${frameworks_dir}/Python.framework/Versions/${py_version}/lib/pkgconfig
for whichever py_version you wanted.
It is not ideal, but is was the best I could come up with at the time.