Re: Packaging patch?

Iwan Vosloo <[email protected]> Sun, 13 Aug 2006 18:08:48 +0200
Newsgroups gmane.comp.python.spyce.general
Message-ID <[email protected]>
On Sun, 2006-08-13 at 05:45 -0700, Jonathan Ellis wrote:
> On Sat, 12 Aug 2006 12:09:03 +0200, "Iwan Vosloo" <[email protected]> said:
> > How it's done is - I added a setup.py which uses setuptools to make a
> > spyce egg.  This egg is then packaged in a .deb.  (Of course, the egg is
> > handy for installation on windows machines too, and with the setup.py
> > you can easily build rpms too.)
> 
> Pauli has also created debian packaging scripts, which I forwarded to
> you.  But maintaining the separate build scripts could get painful.  (We
> also want to add back a Windows installer.)  If we could run all of
> these from setuptools that would be a big win IMO.

Yea.  That's the idea.  The debian bits are a bit of a duplication, but
are dependent on the egg built by the setuptools setup.py.  With
setuptools you can build an rpm and exe and tar.gz from the egg.  But
not a deb.

I'm a bit snowed under at the moment - will try to look at what Pauli
has done within the next 2 weeks.  Perhaps I can send a setup.py and
adapt Pauli's stuff to use that.  You can then figure out what to do
with the makefile.  (I usually keep a makefile, but change some make
targets over to run python setup.py <xxx>.)

> > You have to manually run your makefile before building the egg.  And, as
> > of NOW I'm still not packaging it according to the new debian python
> > policy.
> 
> What does that mean?

2 Things:
- Debian is in the process of changing their python packaging policy.  I
suspect that the next version of Ubuntu will adhere to it.  It affects
the package names (which included the python version), for example, and
where things are installed.  I still have to get to grips with the
details of the new policy...

- I did not want to touch your makefile.  Setuptool's setup.py
duplicates a makefile's functionality somewhat.  But only somewhat.  Its
not as general-purpose a thing as make, and you have all kinds of
targets in that makefile that are useful to you which I did not need.
One I do need is your 'docs' target.  If you want to include the output
of 'make docs' in an egg, you will have to execute 'make docs' first.  I
opted for redundancy (between the makefile and the setup.py), so that my
added bits do not interfere with upstream changes from you.



-i


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642