Ted,

Thanks for your response.

It has been our experience that there are dependencies between packages that is 
not clearly or explicitly described. Which has lead us to the belief that order 
of installation is important.

For instance both the C++ and Java Brokers.  Only after they are installed does 
it become clear that the Python tools are necessary for the configuration of 
the broker.  

It is these subtle dependencies that have us wondering if there is any explicit 
guidance as to the proper order in which to install each of these packages.  

Again the intent is to provide guidance so that development environments are 
setup in a consistent and "standard" manner.  At the very least so we can 
standup a standard VM image for our developer "on boarding" process.

Regards,

Paul

________________________________________
From: Ted Ross [[email protected]]
Sent: Thursday, March 03, 2016 7:49 AM
To: [email protected]
Subject: Re: General Question:  Is there an implied order of installing QPID 
packages?

On 03/02/2016 06:17 PM, Flores, Paul A. wrote:
> Is there a order in which Qpid packages should be installed in?
>
>
>
> Proposed development environment to use C++ (Broker & Proton) and Java.
>
>
>
> Looking for guidance for getting developer RHEL 7 environments setup.

Your best bet for RHEL7 is to enable the EPEL7 (Extra Packages for
Enterprise Linux) repo and simply "yum install" the desired development
packages.  EPEL7 has the latest upstream qpidd, proton, and dispatch
packages.

I'm not sure if the Qpid Java components are packaged here.  These may
need to be installed from upstream.

http://fedoraproject.org/wiki/EPEL


>
>
>
> Any suggestions/recommendations/insights are welcomed.
>
>
>
>
>
> Paul
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to