On 10/09/2012 07:48 PM, Chip Childers wrote:
On Tue, Oct 9, 2012 at 12:31 PM, David Nalley <[email protected]> wrote:
On Tue, Oct 9, 2012 at 12:17 PM, Chip Childers
<[email protected]> wrote:
OK,
So let me try to summarize the opinions here:
We have a couple of folks that think it should be split back out, but
more are erring on the side of keeping the functionality.
Assuming that we keep the code in the ACS repo for now, the second
question is one of packaging. Wido proposed a "cloudbridge" package
for this specific code. I think that makes sense, in that it gives us
options for breaking apart from CS in the future.
Can we get some opinions about the packaging specific portion of the issue now?
So we release source code - so from a release perspective I think it
makes next to no difference.
For the convenience binaries that are being built it might make a
tremendous amount of difference - up to an including functionality not
working
I'd specifically not want to substantially change RPMs at this stage.
Debs could have this broken out since it has never been there, but it
would all need to be tested.
--David
OK, so let's move forward with this plan:
1 - Get the DEB package built (as a separate package).
This will be hard. Since we have a central control file for the Debian
packaging it will be something like cloud-awsapi or cloud-bridge
In the spec file I saw that that cloud-awsapi is depending on
cloud-deps, so that starts to tie it in with the rest of the code-base
on a packaging level.
2 - Test the AWS API via a DEB package installation
We don't touch the RPM's now, since it's already been tested and (as
of this morning) validated as working.
Does someone want to pick up the DEB packaging for Wido (since I
assume he's sleeping right now)?
Not a sleep yet :) I'll be offline soon though, but I can follow up on
work done over night (for me) and continue in the morning on what Edison
came up with.
Wido
-chip
