Hi all,
Would you know a tutorial on Debian packaging from buildout/distribute?
I mean:
- I setup the buildout.cfg
- I run buildout with Z or X option
- I get the package
I dont mind if it's not entirely Debian compatible
(python and some libs duplication).
Any link?
Thank you.
--
On Thu, Sep 17, 2009 at 21:05 +0200, Wolodja Wentland wrote:
On Thu, Sep 17, 2009 at 18:51 +0200, Tarek Ziadé wrote:
you might be able to alter it on-the-fly by overriding the build_py command
instead of the install command
That worked perfectly! Thanks again for the help and pointers you
Hi,
for the folks using virtualenv-distribute, i forked it to make the last 0.6.3
install instead of 0.6.1.
See :
http://bitbucket.org/kiorky/virtualenv-distribute/
Install it:
easy_install
http://distfiles.minitage.org/public/externals/minitage/virtualenv-distribute-1.3.5dev-1.zip
Ned Deily
Hi,
I'm planning to make a port for Distribute to make it more accessible to users.
However, thinking about up coming 0.7 release, which will break the
compatibility
with setuptools, I started wondering it's not so easy to make a
package for distribute.
If I understand correctly, Distutils 0.7
On Sun, Oct 4, 2009 at 5:10 PM, Akira Kitada akit...@macports.org wrote:
I'm planning to make a port for Distribute to make it more accessible to
users.
That's very much appreciated :)
For Distribute, there would be a few options to work around this:
1) Make 0.6 and 0.7 different package,
At 03:49 PM 10/3/2009 +0200, Tarek Ziadé wrote:
Notice that this has been fixed in Ubuntu already with a patched
version of setuptools
Is the patch or an equivalent already in the setuptools tracker? And
if not, can someone please post it there? Thanks.
New submission from Ned Deily n...@acm.org:
A change in distutils distributed with Python 2.6.3 breaks setuptools. Builds
of
extension modules fail with n get_ext_filename ext = self.ext_map[fullname]
KeyError: 'xx'. An analysis and patch is documented in the Distribute
tracker
issue 41:
stdeb produces Debian source packages from Python packages via a new
distutils command, sdist_dsc. Automatic defaults are provided for the
Debian package, but many aspects of the resulting package can be
customized via a configuration file. An additional command, bdist_deb,
creates a Debian binary
On Sun, Oct 4, 2009 at 5:28 PM, Hanno Schlichting ha...@hannosch.eu wrote:
For Distribute, there would be a few options to work around this:
1) Make 0.6 and 0.7 different package, like Distribute and Distribute2
(Jinja like solution)
2) Make 0.7 fat package, which includes 0.6(setuptools
On Sun, 04 Oct 2009 13:41:06 -0700, Tarek Ziadé ziade.ta...@gmail.com
wrote:
The other way would be to use Distribute instead of Setuptools for
what the packaging system is calling setuptools. That's pretty
much what is happening in Gentoo (arch) and UHU-Linux (dev),
right now
Interesting.
Sridhar Ratnakumar a écrit :
On Sun, 04 Oct 2009 13:41:06 -0700, Tarek Ziadé ziade.ta...@gmail.com
wrote:
The other way would be to use Distribute instead of Setuptools for
what the packaging system is calling setuptools. That's pretty
much what is happening in Gentoo (arch) and UHU-Linux
10/04/2009 11:23 PM, Tarek Ziadé:
What package exactly ? I am not sure to understand
Everything installable with buildout.
Example: Plone. I want a debian Plone package.
I configure buildout properly, run it with some appropriate options
and abracadabra the .deb is there.
The same with grok,
12 matches
Mail list logo
