[ python-Bugs-1000623 ] Compound package errror

[noreply at pgfoundry.org]

Bugs item #1000623, was opened at 2006-05-01 06:39
You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1000623&group_id=1000094

Category: None
Group: Performance Issue
Status: Closed
Resolution: Accepted
Priority: 3
Submitted By: Adrian Klaver (aklaver)
Assigned to: Nobody (None)
Summary: Compound package errror

Initial Comment:
Running the setup.py file from the postgrespy-0.1 package does not build and install the backend components. I looked at the setup.py file and the be directory is not included. I tried adding it with no success. As a side note there is a reference to a ctl directory that does not exist in my installation. To get the backend to build I had to descend into the be directory and run the setup.py in that directory.

----------------------------------------------------------------------

>Comment By: James Pye (jwp)
Date: 2006-05-06 16:03

Message:
Ok, that sounds good; will add info to the README. I was actually intending pkg to be more general(ie, seperate packages for be and fe), but it certainly seems like it's best to just throw everything in there and sort it all out.

ctl is short for "control"--current code/version name "boss". It is a set of modules that provide Python interfaces to PostgreSQL management "routines". Literally, this is Python interfaces to initdb and pg_ctl commands, a configuration editor(which has some simple smarts), and soon an hba editor with similar smarts. It's going to be a dependency of tin(Test INfrastructure), which will be tool for managing/using PostgreSQL test environments.

----------------------------------------------------------------------

Comment By: Adrian Klaver (aklaver)
Date: 2006-05-06 15:00

Message:
I understand the be issue now. The only further comment I 
can make is that it would be nice if the separate build 
requirement is mentioned in the README. Just for the 
record what is ctl? 

----------------------------------------------------------------------

Comment By: James Pye (jwp)
Date: 2006-05-04 21:14

Message:
The backend component needs to be built separately. Considering that a system can have multiple PostgreSQL installations, it seemed inappropriate to just build it against the first found PostgreSQL. All the other projects are very straight forward with their distutils use, so it is very trivial to tie them in the way that I do. However, I dread working in 'be' in the same fashion(be makes special distutils commands and uses a Distribution subclass). I have been invisioning a special, interactive script for installing the backend. It seems difficult enough to justify such a thing. :(
(not to mention, it also uses a module found in layout, tho, I suppose it could be made to reference that locally)
[mm, if you would like to discuss this more, I think it might make a good thread on the list]

[about ctl..]
Oh, you got the first package that I bundled. Yeah, I forgot the 'ctl' directory; it is in the new one. Sorry for the omission.

----------------------------------------------------------------------

You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1000623&group_id=1000094