On 08/04/2011 05:01 PM, Alexis Richardson wrote:
I have bcc'd Hubert.
On Thu, Aug 4, 2011 at 3:49 PM, Peter Lemenkovwrote:
I wasn't offended. I used to be able to do updates fairly regularly butI have bcc'd Hubert.
On Thu, Aug 4, 2011 at 3:49 PM, Peter Lemenkovwrote:
2011/8/4 David Wragg<david at rabbitmq.com>:
hardcoded paths and variables and other ugly stuff like that) to
manage issues like these (automatic Erlang dependency extraction). We
(I and one brave intern from Erlang Solutions, Micha? Nie?) planned to
finish this task during GSoC but, unfortunately, we didn't get chosen.
Anyway I plan to return to this task as soon as I find free time, so
stay tuned.
As for RabbitMQ, I'll take a look - perhaps I could slim dependency
chain manually (with these semi-automatically working scripts
mentioned above).
BTW where is Hubert Plociniczak? Is he still around? I'm afraid that
he was offended by the angry mob after unsuccessful RabbitMQ 2.1
release:
https://bugzilla.redhat.com/show_bug.cgi?idd6861
Massimo Paladin<Massimo.Paladin at cern.ch> writes:
relatively recently (about a year ago, I think). So depending on the
sub-packages would limit which releases of distributions our RPM will
work on.
So, in order to support a wide range of distributions, our RPM still
depends simply on "erlang".
I expect we will reconsider this one day, but it is probably still too
early today.
I already wrote semi-automatically working bunch of scripts (withRabbitMQ RPM requires erlang which is provided by a lot of
sub-packages.
The Fedora/EPEL erlang RPM only got separated up into many packagessub-packages.
relatively recently (about a year ago, I think). So depending on the
sub-packages would limit which releases of distributions our RPM will
work on.
So, in order to support a wide range of distributions, our RPM still
depends simply on "erlang".
I expect we will reconsider this one day, but it is probably still too
early today.
hardcoded paths and variables and other ugly stuff like that) to
manage issues like these (automatic Erlang dependency extraction). We
(I and one brave intern from Erlang Solutions, Micha? Nie?) planned to
finish this task during GSoC but, unfortunately, we didn't get chosen.
Anyway I plan to return to this task as soon as I find free time, so
stay tuned.
As for RabbitMQ, I'll take a look - perhaps I could slim dependency
chain manually (with these semi-automatically working scripts
mentioned above).
BTW where is Hubert Plociniczak? Is he still around? I'm afraid that
he was offended by the angry mob after unsuccessful RabbitMQ 2.1
release:
https://bugzilla.redhat.com/show_bug.cgi?idd6861
because of my current work responsibilities (I do not work for rabbitmq)
I have little time for my other hobbies (like fedora packaging).
So if there is any good soul with decent understanding of fedora
packaging process and erlang/rabbitmq knowledge then I would be willing
to pass it over to him/her.
Thanks Alexis for including me in the conversation, I admit I rarely
look into this mailing list nowadays.
Thanks,
hubert
--
With best regards, Peter Lemenkov.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
With best regards, Peter Lemenkov.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
