Hello,

RabbitMQ RPM requires erlang which is provided by a lot of sub-packages.

I wonder if rabbit really needs all those sub-packages,
did someone already spend some time shrinking down the required erlang
sub-packages?

Regards,
---
Massimo Paladin

email: massimo.paladin at gmail.com
website: http://www.mpaladin.com
flickr's page: http://flickr.com/photos/massimop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110804/169061c3/attachment.htm>

Search Discussions

  • Matthias Radestock at Aug 4, 2011 at 11:30 am

    On 04/08/11 12:18, Massimo Paladin wrote:
    RabbitMQ RPM requires erlang which is provided by a lot of sub-packages.

    I wonder if rabbit really needs all those sub-packages,
    did someone already spend some time shrinking down the required erlang
    sub-packages?
    We used to depend on just the packages the broker needs. However,
    plug-ins may use more packages than the broker.

    Matthias.
  • Simon MacMullen at Aug 4, 2011 at 11:34 am

    On 04/08/11 12:30, Matthias Radestock wrote:
    On 04/08/11 12:18, Massimo Paladin wrote:
    RabbitMQ RPM requires erlang which is provided by a lot of sub-packages.

    I wonder if rabbit really needs all those sub-packages,
    did someone already spend some time shrinking down the required erlang
    sub-packages?
    We used to depend on just the packages the broker needs. However,
    plug-ins may use more packages than the broker.
    We used to do that for Debian, not RPMs. I think RPMs having
    sub-packages at all is fairly recent.

    Unfortunately to my untutored eye it still doesn't look like there's any
    equivalent of Debian's erlang-nox metapackage, so we drag in all sorts
    of X11 deps we don't need.

    Cheers, Simon

    --
    Simon MacMullen
    RabbitMQ, VMware
  • Massimo Paladin at Aug 4, 2011 at 12:36 pm
    There are 56 sub-packages, I don't know erlang, could you try to guess a
    subset of these?

    erlang-snmp
    erlang-sasl
    erlang-cosEventDomain
    erlang-erts
    erlang-debugger
    erlang-test_server
    erlang-percept
    erlang-stdlib
    erlang-typer
    erlang-pman
    erlang-gs
    erlang-orber
    erlang-common_test
    erlang-kernel
    erlang-compiler
    erlang-et
    erlang-inets
    erlang-cosTime
    erlang-tv
    erlang-appmon
    erlang-jinterface
    erlang-mnesia
    erlang-dialyzer
    erlang-tools
    erlang-edoc
    erlang-cosFileTransfer
    erlang-ic
    erlang-syntax_tools
    erlang-wx
    erlang-ssl
    erlang-webtool
    erlang-cosProperty
    erlang-docbuilder
    erlang-inviso
    erlang-crypto
    erlang-hipe
    erlang-megaco
    erlang-cosEvent
    erlang-otp_mibs
    erlang-reltool
    erlang-parsetools
    erlang-erl_docgen
    erlang-asn1
    erlang-ssh
    erlang-eunit
    erlang-runtime_tools
    erlang-odbc
    erlang-os_mon
    erlang-examples
    erlang-xmerl
    erlang-observer
    erlang-cosTransactions
    erlang-erl_interface
    erlang-public_key
    erlang-cosNotification
    erlang-toolbar

    Regards,
    ---
    Massimo Paladin

    email: massimo.paladin at gmail.com
    website: http://www.mpaladin.com
    flickr's page: http://flickr.com/photos/massimop

    On Thu, Aug 4, 2011 at 1:34 PM, Simon MacMullen wrote:
    On 04/08/11 12:30, Matthias Radestock wrote:
    On 04/08/11 12:18, Massimo Paladin wrote:

    RabbitMQ RPM requires erlang which is provided by a lot of sub-packages.

    I wonder if rabbit really needs all those sub-packages,
    did someone already spend some time shrinking down the required erlang
    sub-packages?
    We used to depend on just the packages the broker needs. However,
    plug-ins may use more packages than the broker.
    We used to do that for Debian, not RPMs. I think RPMs having sub-packages
    at all is fairly recent.

    Unfortunately to my untutored eye it still doesn't look like there's any
    equivalent of Debian's erlang-nox metapackage, so we drag in all sorts of
    X11 deps we don't need.

    Cheers, Simon

    --
    Simon MacMullen
    RabbitMQ, VMware
    ______________________________**_________________
    rabbitmq-discuss mailing list
    rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
    https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110804/b2bf0e7e/attachment.htm>
  • David Wragg at Aug 4, 2011 at 2:20 pm

    Massimo Paladin <Massimo.Paladin at cern.ch> writes:
    RabbitMQ RPM requires erlang which is provided by a lot of
    sub-packages.
    The Fedora/EPEL erlang RPM only got separated up into many 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.

    (Unlike RPM, dpkg supports disjunctions of dependencies, so our Debian
    packages don't present this dilemma.)

    --
    David Wragg
    Staff Engineer, RabbitMQ
    VMware, Inc.
  • Peter Lemenkov at Aug 4, 2011 at 2:49 pm

    2011/8/4 David Wragg <david at rabbitmq.com>:
    Massimo Paladin <Massimo.Paladin at cern.ch> writes:
    RabbitMQ RPM requires erlang which is provided by a lot of
    sub-packages.
    The Fedora/EPEL erlang RPM only got separated up into many 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.
    I already wrote semi-automatically working bunch of scripts (with
    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
    --
    With best regards, Peter Lemenkov.
  • Alexis Richardson at Aug 4, 2011 at 3:01 pm
    I have bcc'd Hubert.
    On Thu, Aug 4, 2011 at 3:49 PM, Peter Lemenkov wrote:
    2011/8/4 David Wragg <david at rabbitmq.com>:
    Massimo Paladin <Massimo.Paladin at cern.ch> writes:
    RabbitMQ RPM requires erlang which is provided by a lot of
    sub-packages.
    The Fedora/EPEL erlang RPM only got separated up into many 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.
    I already wrote semi-automatically working bunch of scripts (with
    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
    --
    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
  • Hubert Plociniczak at Aug 5, 2011 at 6:42 am
    Hi all,
    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:
    2011/8/4 David Wragg<david at rabbitmq.com>:
    Massimo Paladin<Massimo.Paladin at cern.ch> writes:
    RabbitMQ RPM requires erlang which is provided by a lot of
    sub-packages.
    The Fedora/EPEL erlang RPM only got separated up into many 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.
    I already wrote semi-automatically working bunch of scripts (with
    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
    I wasn't offended. I used to be able to do updates fairly regularly but
    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
  • Simon MacMullen at Aug 5, 2011 at 10:04 am

    On 05/08/11 07:42, Hubert Plociniczak wrote:
    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.
    I should note that we (the RabbitMQ team) tend to make changes to the
    RPM spec as needed, so someone closer to the Fedora end could work out.

    Cheers, Simon

    --
    Simon MacMullen
    RabbitMQ, VMware

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedAug 4, '11 at 11:18a
activeAug 5, '11 at 10:04a
posts9
users7
websiterabbitmq.com
irc#rabbitmq

People

Translate

site design / logo © 2022 Grokbase