[Crowbar] Separate, per barclamp locale files
rhafer at suse.de
Tue Jul 24 08:55:16 CDT 2012
On Dienstag 24 Juli 2012 08:28:37 Rob_Hirschfeld at Dell.com wrote:
> You're right. It looks like we can simply allow each barclamp to
> maintain its own file and I18N will handle the merge.
> I'm working on a similar issue for navigation & DB migrations, I'll
> give it a test and see if we can make the change.
Cool. Yeah, navigation is causing us similar issues currently :)
> -----Original Message-----
> From: crowbar-bounces On Behalf Of Ralf Haferkamp
> Sent: Tuesday, July 24, 2012 4:16 AM
> To: crowbar
> Subject: [Crowbar] Separate, per barclamp locale files
> is there a specific reason why all the locale additions are merged into
> the single en.yml file during barclamp_install?
> Installing and uninstalling barclamps (independed of if that happens
> via a RPM/DEB package of from tarballs) would seem to be quite a bit
> simpler if every barclamp cloud just drop its own locale additions as
> a separate file into a specific directory (e.g.
> Uninstalling would just be a matter of delete that file again. This
> would get as rid of the error prone merge step in barclamp_install.
> Merging everything into a single file is especially problematic when
> trying to package barclamps as rpms or debs as upgrading the crowbar-
> barclamp will just overwrite all changes to the main en.yml.
> BTW, shouldn't the locale additions just be in a separate file in the
> barclamps from the beginnig, instead of having them as a separate
> section in the crowbar.yml?
> Crowbar mailing list
> Crowbar at dell.com
> For more information: https://github.com/dellcloudedge/crowbar/wiki
SUSE LINUX Products GmbH,
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
HRB 16746 (AG Nuernberg)
More information about the Crowbar