On 04/18/2013 08:34 PM, Jon Dowland wrote:
> Hi,
>
> I saw this bug and I got a bit concerned.
We used to use python ObjConfig, but it's not compatible with Openstack
.ini files...
> I'm a likely user of the
> openstack packages in Debian — well I/we could be, if they fit our
> needs — but I'm r
Hi,
I saw this bug and I got a bit concerned. I'm a likely user of the
openstack packages in Debian — well I/we could be, if they fit our
needs — but I'm really worried that they are going to be vastly
over-engineered. In a way it reminds me of the exim4 packages: the
situation is not entirely ana
On Tue, Mar 19 2013, Thomas Goirand wrote:
> Who's problem then?
I don't know -- I'm not sure it's a even problem. Maybe dpkg's problem?
> I thought like you first. Then I realized that we have no choice but to
> implement something anyway, because the upstream library doesn't have a
> feature t
On 03/19/2013 05:18 AM, Julien Danjou wrote:
> I think you're wrong. The fact that question aren't asked all in a row
> is not the OpenStack packaging team's problem here
Who's problem then?
> and trying to avoid
> this problem by re-implementing something that you will endless run
> after is a w
On Mon, Mar 11 2013, Thomas Goirand wrote:
Hi Thomas,
> I don't want the 2nd version. Openstack operator all want to answer all
> questions, then go to the coffee machine and rest 10 minutes during the
> setup... ;)
>
> So, I continue to think that everything should be done in shell script.
> Not
Hi,
This often happens when one do some code: you hack, hack and hack
around, then after a while, you realize your code need some clean up.
I'm at this point in time with the ini parsing functions in all core
packages of Openstack.
As we're supposed to be a team (even though I really feel too muc
6 matches
Mail list logo
