On 12/18/2012 12:17 AM, Thierry Carrez wrote:
Thomas Goirand wrote:
[No pun intended, but it'd be nice if stackers had a bit more
consideration for our work in Debian, and stop thinking only with
Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, ... in mind.]
There is nothing Ubuntu-specific
Thomas Goirand wrote:
On 12/18/2012 12:17 AM, Thierry Carrez wrote:
Thomas Goirand wrote:
[No pun intended, but it'd be nice if stackers had a bit more
consideration for our work in Debian, and stop thinking only with
Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, ... in mind.]
There is
On 12/18/2012 05:29 PM, Sascha Peilicke wrote:
On 12/17/2012 04:47 PM, Thomas Goirand wrote:
This
means that absolutely all of our packages have to embed a patch in
debian/patches to fix the wrong MANIFEST.in.
We've spent quite some time on that. Or rather, should I say: it's a
real time
Thomas Goirand wrote:
[No pun intended, but it'd be nice if stackers had a bit more
consideration for our work in Debian, and stop thinking only with
Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, ... in mind.]
There is nothing Ubuntu-specific in this. And nothing bzr-specific
either. Fedora
On 12/04/2012 11:01 PM, Nah, Zhongyue wrote:
Is it possible to generate a MANIFEST.in file using setuptools-git? Would
that solve simplicity and efficiency?
Please join the discussion on openstack-dev@. It was my mistake sending
this technical proposal to this ML initially.
Sent from my
Currently, the majority of OpenStack components make use of the Python
module setuptools_git in order to install additional configuration
files. This is basically the same functionality that the MANIFEST.in
file (setuptools/distribute) provides, but automatic. However, we
recently discovered that
Sascha Peilicke wrote:
Currently, the majority of OpenStack components make use of the
Python module setuptools_git in order to install additional
configuration files. This is basically the same functionality that
the MANIFEST.in file (setuptools/distribute) provides, but
automatic.
Note:
Is it possible to generate a MANIFEST.in file using setuptools-git? Would that
solve simplicity and efficiency?
Sent from my iPhone
On Dec 4, 2012, at 9:07 PM, Thierry Carrez thie...@openstack.org wrote:
Sascha Peilicke wrote:
Currently, the majority of OpenStack components make use of the
8 matches
Mail list logo