On Wednesday, February 6, 2013, Pradeep Soundararajan wrote: > Thanks Hugo, Wido and Noa for bringing this to some closure :) > > I am able to package rpm using "packaging/centos63/package.sh" after some > modification in the package.sh script since cloud.spec is looking for > 'cloudstack' Name. > > ------------------------------------------------------------------------ > -mkdir -p $RPMDIR/SOURCES/cloud-$VERSION > +mkdir -p $RPMDIR/SOURCES/cloudstack-$VERSION > > > -(cd ../../; tar -c --exclude .git --exclude dist . | tar -C > $RPMDIR/SOURCES/cloud-$VERSION -x ) > -(cd $RPMDIR/SOURCES/; tar -czf cloud-$VERSION.tgz cloud-$VERSION) > +(cd ../../; tar -c --exclude .git --exclude dist . | tar -C > $RPMDIR/SOURCES/cloudstack-$VERSION -x ) > +(cd $RPMDIR/SOURCES/; tar -czf cloudstack-$VERSION.tgz > cloudstack-$VERSION) > ------------------------------------------------------------------------- > > Packaging went fine after the above modification but I have observed some > issues while installing the package. I believe you have changed the > installation path from */cloud/* to */cloudstack/* and also observed you > have changed all the rpm names from cloud* to cloudstack*. If that is a > situation then I feel we cannot upgrade from 4.0 since they were pointing > to different rpm names and they were loaded in a different location. I > feel, this would raise lot of compatibility issues here and there. > > So we are using things like Obsoletes and Provides in RPM (and their alternatives in deb land) so that the new packages provide cloud- packages and also obsolete the old ones (effectively creating a case where the old packages simply won't be around)
> Noticed you have changed cloud-client to cloudstack-management. I feel, we > have to modify install.sh script accordingly in order to satisfy all the > changed conditions. > There is no install.sh in Apache CloudStack.
