Tom Mueller wrote:
Michal,
Generally, the setup.py file has been targeted towards those parts of
the build that are portable across various platforms. The Makefile is
responsible for doing the part of the build that is only done on
OpenSolaris (such as building the SVR4 packages).
The Makefile calls into the setup.py file as one of its actions, so
developers on OpenSolaris can just run make, while developers on
other platforms just run setup.py.
Since this appears to be Unix only, maybe it would be better to just
integrate this into the to
Tom,
I was thinking about this, but there is one problem which I don't know
how to solve in the Makefile. Basically if the tarballs are missing we
need to download them somehow, which was done in the setup.py for few
packages. Any idea what would be the best way of doing that?
Michal
p level Makefile.
Tom
Michal Pryc wrote:
Hello,
Currently I am integrating automated tests for Package Manager in the
IPS gate, I have most of the parts ready, but one - LDTP package
which is needed to run the tests.
LDTP is python app, but it doesn't have setup.py build system. To
build it we need to:
- setup the proper environment variables.
- run configure and make commands
- package SUNWldtp
Now my question is what would be the best way of building LDTP
package. I have started hacking setup.py file to simply add another
function which will setup environment variables and run subprocess
with configure, make and make install commands and then restore the
previous environment variables.
Please let me know if this is the correct way of building LDTP
package or there is a better one?
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
