[Glass] How to convert this source to GsDevKit_stones ?

Marten Feldtmann m at feldtmann.online
Tue Nov 26 14:50:03 PST 2024


Hey,

well GsDevKit_stones/bin and superDoit/bin are in my PATH variable, so I
have no problems calling all stuff from there.

Well, I asked ChatGPT how to get the GEMSTONE variable value from the
input parameter stoneName, registryName and $stones_data_home value
considering the structure of GsDevKit_stones and this resulting bash
script seems to work. With that I can start all other processes.


By the way:

* what are projectsets for ????
* how can I create own stone templates from full backups of a GS database ?

Thanks

Marten

On 26.11.24 21:52, Dale Henrichs wrote:
>
>
> On Tue, Nov 26, 2024 at 12:04 PM Marten Feldtmann <m at feldtmann.online>
> wrote:
>
>     Hello Dale,
>
>     I look at it and I don't get it :-(
>
>     a) I have no GsDevKit_home any more on my new deployment machines
>     - so GS_HOME is not set any more, only GsDevKit_stones and
>     superDoit is on these machines ... so the second usage is not possible
>
> I don't see anywhere where I mention GsDevKit_home other than where I
> quoted your comment, so I'm not sure what you are complaining about...
>
>
>     b) For the first usage example I need to set the GEMSTONE variable
>     ... and how to get this value in a simple way was the main part of
>     my question.
>
> Okay ... I made the assumption that you had installed GsDevKit_stones
> following the instructions in the README[1], where superDoit/bin needs
> to be in your path ... AND I mispoke claiming that only
> GsDevKit_stones/bin needed to be in your path ... I should have said,
> "followed the GsDevKit_stones installation instructions"
>
> I also want to point out ... that currently superdoit_topaz does not
> properly set the environment variables from the customenv file in the
> stone directory and that is a bug in superDoit (issue #66[2]) that
> will need to be fixed before you can avoid having to use a shell
> script to source the customenv file. BTW,
> GsDevKit_stones/bin/customenv.solo is the script that can be used to
> set/unset the env vars in customenv.
>
> I suppose it wouldn't hurt at this point to share the SHA of the
> commits that you are using for GsDevKit_stones and superDoit so we can
> make sure that we're all on the same page ... I'm looking at
> GsDevKit_stones:4420d133d and superDoit:e69e3ff7a.
>
> Dale
>
> [1]
> https://github.com/GsDevKit/GsDevKit_stones/tree/v2.1?tab=readme-ov-file#installation
> [2] https://github.com/dalehenrich/superDoit/issues/66

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20241126/b88fd9d9/attachment-0001.htm>


More information about the Glass mailing list