Hi there László, James and others.
On Mon, Oct 28, 2013 at 10:53 AM, László Böszörményi (GCS)
<[email protected]> wrote:
> On Sun, Oct 27, 2013 at 12:40 PM, Rogério Brito <[email protected]> wrote:
>> Package: mongodb-server
>> Version: 1:2.4.5-1
> Please check your changes with the latest Debian uploaded version,
> 1:2.4.6-1 ATM.
I can't check them running, because mongodb is not build for i386
right now (which is what I am using). I will side-grade this machine
to be amd64, but real life will probably only allow me such a luxury
on December.
>> In April of this year, I started playing with mongodb and made many
>> improvements to the package:
> [...]
>> Now that I see that fresh blood has started to work on mongodb, I would like
>> to resume my contributions and, before that, I would kindly ask that you
>> consider integrating or reviewing the modifications that I sent to the
>> previous repository:
> To be honest, I'm not that fresh, being 36 years old. :)
Hey, I meant fresh blood as in enthusiasm, not age. :) (I am a bit
older than you). :)
> But I'm not
> fresh anyway as I was in touch with MongoDB already due to my
> php5-mongodb and syslog-ng packages.
Great. I am mostly a novice with mongodb, having only been introduced
to it because I saw that 10gen was offering online courses and I liked
it so much that I concluded their M101P, M101J, and M102. :)
> I'll do my best to get the package in a good shape soon.
Yes, the package sucks right now. There is soooo much duplication
(apart from the embedded libraries, which I tried to work to bring
down to some sane levels) and I think that I succeeded partially. But,
now, the clients are simply *huge* and they don't need to be.
> ATM I'm waiting for the boost1.54
> bugfix[1] to build MongoDB again on 32 bit archs.
Good.
> Then I plan to include systemd support and correct the copyright file with the
> AGPL+OpenSSL license exception.
Excellent. I was going to file a bugreport (actually, more of a
question) to the Ubuntu people asking them if they asked for legal
clarifications from 10gen about this part, but, as I told you before,
I lost interest, because I was very excited, but the previous
maintainer didn't react in a timely fashion.
In fact, James opened a pull request on github that is 6 months old
and I pinged the previous maintainer more than once about the package.
I had a commit including my name in the uploaders field which, I then,
reverted with appropriate comments:
https://github.com/rbrito/mongo-debian/commit/cf1c1fa6
> Then MongoDB should be built on all
> architectures[2] that V8 supports.
That would be great. I have worked a bit on applying, testing etc. the
patches contributed to make the kfreebsd port working.
Oh, and I just saw that you migrated away from CDBS! Halleluiah!
> I think these are the most
> important changes needed to the packaging. James, what do you think?
Great.
>> If you guys need/want a helping hand, please let me know and I will try to
>> help as best as I can.
>
> Feel free to contact me whenever you feel like so. I consider James a
> friend of mine (we are in contact for other things as well) and I
> suspect that he also accept any help from you. Anyway, I'll work with
> him to eliminate any differences between Debian and Ubuntu packages of
> MongoDB.
I hope that the differences can also be as small that they won't even
have any patches applied on top of Debian's and we should, of course,
push anything non-distro-specific upstream.
After my public rant, I saw that James is a person with whom it is
quite feasible to work with and I look forward working with him.
I have commit access to collab-maint, but I think that, at this state,
it will be better if I simply send pull requests and/or patches via
git-send-email, but for the latter, which e-mail should I use?
Thanks for the kind reception,
Rogério.
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
