Hi, > I don't really get it: if it's of little use outside of CERN, why > should this be done in new installs?
1] CERN uses Savane as it is available from GNA and therefore it is in CERN's interest that mods which are important to CERN get commited to the trunk and therefore get included in future versions that CERN may download and install. 2] However, this particular change (that I made and installed in the production version at CERN) is probably of little importance or useless for most if not all other installations and therefore does NOT justify that people update their savane database via an upgrade kit. They will anyhow inherit this mod when a new version of Savane get installed on their system. Yves On Thu, 26 Apr 2007, Sylvain Beucler wrote: > On Thu, Apr 26, 2007 at 04:04:19PM +0200, Yves Perrin wrote: > > Hi, > > > > > Modified: > > > trunk/db/mysql/table_patch_field_usage.initvalues > > > > > > Should this be also changed in existing databases? > > > (eg should there be a update/3.1/ upgrade script?) > > > > In my opinion NO ! > > ... given that: > > 1] the patch tracker, although heavily used at CERN, > > seems to be more or less 'unused/abandoned' elsewhere. > > 2] the 'export' facility, although getting more popular, > > is probably little used outside CERN. > > Cheers, > > Yves > > Hi, > > I don't really get it: if it's of little use outside of CERN, why > should this be done in new installs? > > Maybe I don't grasp exactly what this change is about. > > -- _______________________________________________ Savane-dev mailing list [email protected] https://mail.gna.org/listinfo/savane-dev
