Awesome. The branch is now ready for merge.
Essentially, this is the same code, but renamed to be less horrible to
type/say + cleaned up / updated. Everything is now a python unittest
module (except for the dtr stuff).
This enables us to write tests in Python, so we are less likely to bang
Hi!
lp:libdrizzle lives again!
It is just a pull from the lp:drizzle that has been chopped down. The plan is
to maintain it for folks who just want libdrizzle.
Cheers,
-Brian
signature.asc
Description: Message signed with OpenPGP using GPGMail
Hi,
We could choose to not install the version of libdrizzle that we ship with the
server. Or,... put it into a different directory on install
Cheers,
-Brian
On Feb 3, 2012, at 4:42 AM, Henrik Ingo wrote:
Ah. Turns out this isn't feasible. Of course if using just one spec
file,
Hi everyone,
The final branches that are in the merge queue are being merged into
trunk and once that is done we are going to do a release candidate. Once
the release candidate is cut we wontdo any more merges till after the GA.
And, there will be a total of 2 - 3 release candidates. So, if you
Hi Brian
Did you figure out what to do with versioning and such?
The more I think about it, the more I went back to the idea that when
it comes to packages, libdrizzle could continue to be released
together with drizzled, and only that. After all, the original request
was for someone who wanted
Ah sorry, I just asked a question and didn't read all my emails to
find out you already answered it.
Anyway, in the other thread I outlined a proposal where libdrizzle
releases would still mostly coincide and use same versions as the
server (while also providing lp:libdrizzle for people that want
6 matches
Mail list logo
