Re: [Gusdev-gusdev] meta, update, commit, etc...

[Steve F. <sfi...@pc...>]

Michael-

you should only need to run +meta iff GusApplication.pm has changed.

stefe

MICHAEL LUCHTAN wrote:

>Steve-
>Thanks... Concating to  the cvs revision number in the code is how we
>got around the previous problem with GBParser.  I've got my original
>problem/plugin solved/working, but just as a clarification, how often do
>you need to run ga +meta --commit?  It seems everytime that I try to
>register a new plugin with +update --commit it tells me to run ga +meta
>--commit (but maybe that's because I tend to rebuild the whole tree).
>
>Michael Luchtan
>http://www.cs.uga.edu/~luchtan
>
>
>On Fri, 16 May 2003, Steve Fischer wrote:
>
>  
>
>>Michael-
>>
>>Thanks for being persistent and I'm glad that at least so far there's a
>>DONT in your illustrative package name.
>>
>>Yes, it sounds like you got the build down.
>>
>>You have stumbled into what I think is the one remaining "known issue"
>>with ga:  it lets you do a 'ga +meta --commit' when it is not needed,
>>and that does cause an error that needs a minor cleanup.
>>
>>First let me explain what is going on with +update, +create and +meta.
>>
>>The basic idea is that these register a plugin version with the db.  ga
>>will not allow you to run an unregistered version of a plugin (unless
>>you do not use --commit).
>>
>>Use +create when you want to register a plugin with your GUS db for the
>>first time.  This would happen when you first run a plugin at your site.
>>
>>Use +update when you want to run a version of a plugin that is more
>>recent then the one that is registered in your database.  This would
>>happen if:
>>  1. you have installed a new version of the gus software (eg, gotten a
>>new version from cvs), or
>>  2. you have:
>>      a. edited a plugin,
>>      b. cvs checked it in,
>>      c. run the build system
>>
>>
>>This informs the db of the new version of the plugin.
>>
>>Note that step 2 implies that you have developer access to the plugin
>>you are modifying.  For the plugins that are packaged with GUS I think
>>that your group does not have that access.  In other words, as it stands
>>right now, without developer rights, you shouldn't be able modify any of
>>the built-in plugins. Trying to do so should trigger an error when you
>>run ga.  (Which does lead to the question of how you guys were able to
>>hack in the date format change you told me about.  Which file did you
>>make that change in?).
>>
>>Use +meta when you have installed a new version of the GUS software, and
>>'ga' has been upgraded.
>>
>>Because I have not yet gotten the chance to fix ga so it prevents you
>>from running +meta more than once for a particular version of ga, you
>>will need to do a little trick to correct your db.
>>
>>Here is what to do to correct the problem of having run +meta more than
>>once for a given version of ga:
>>   1. edit $PROJECT_HOME/GUS/PluginMgr/lib/perl/GusApplication.pm
>>   2. find the line that looks like this:           cvsRevision =>
>>'$Revision: 1.37 $',
>>   3. what ever revision number is there, change it by adding a ".111"
>>on the end, thereby making it a unique version
>>   4. do a build GUS install -append
>>   5. run ga +meta --commit (only once!)
>>
>>Feel free to call (610) 649-8929
>>
>>steve
>>
>>
>>MICHAEL LUCHTAN wrote:
>>
>>    
>>
>>>Hello all-
>>>I am just getting started with gus, and was wondering if I could get a
>>>little guidence with regards to the versioning system.
>>>Correct me if I am wrong, but the following steps need to be taken when
>>>updating/installing a new module:
>>>1.  Get the module, and make sure that it is in the proper place in the
>>>directory tree.
>>>2.  Run build.
>>>
>>>I think I've got those down, but the next series of steps seem to be a
>>>jumble up.  I've tried all (two)possible permutations and all seem to
>>>grant some kind of error (for purpose of illustration, assume the plugin is
>>>GUS::BUS::DONT::Cuss):
>>>a. ga +update GUS::BUS::DONT::Cuss --commit
>>>b. ga +meta --commit
>>>
>>>Each one seems to require the other one, and if you do them more than
>>>once, you get an user error like:
>>>
>>>USER ERROR: Found more than one Core.AlgorithmImplementation for
>>>exe=GUS::PluginMgr::GusApplication cvsRev=1.37:
>>> algimp_id:87  md5:d17ad6e0d94a36f54b6b91c11df00b76  rev:1.37  tag:
>>> algimp_id:83  md5:920905884ae1197584fccd39b294495b  rev:1.37  tag:
>>> algimp_id:88  md5:d17ad6e0d94a36f54b6b91c11df00b76  rev:1.37  tag:
>>>
>>>And GUS::BUS::DONT::Cuss still doesn't work.
>>>So I have two questions:
>>>1.  What is the correct procedure?
>>>2.  How does one recover from the above error assuming you have executed
>>>statements a,b more than once.
>>>
>>>Michael Luchtan
>>>http://www.cs.uga.edu/~luchtan
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>>>The only event dedicated to issues related to Linux enterprise solutions
>>>www.enterpriselinuxforum.com
>>>
>>>_______________________________________________
>>>Gusdev-gusdev mailing list
>>>Gus...@li...
>>>https://lists.sourceforge.net/lists/listinfo/gusdev-gusdev
>>>
>>>
>>>      
>>>
>>    
>>
>
>
>
>-------------------------------------------------------
>Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>The only event dedicated to issues related to Linux enterprise solutions
>www.enterpriselinuxforum.com
>
>_______________________________________________
>Gusdev-gusdev mailing list
>Gus...@li...
>https://lists.sourceforge.net/lists/listinfo/gusdev-gusdev
>  
>