<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> I add one thing that might be useful, I have a few startup .sh scripts to run Cuis. Because at times i want to start Cuis in its base form, e.g. i want to evaluate recent changes other people made to the code or to test one of my packages. At times i want to run with all my preferred library loaded and other preferences. I put the startup scripts into the cuis-projec[-fooX]/ I put external packages from GiHub as well into cuis-projec[-fooX]/ This way makes it clear to me that each first level sub-directory of cuis-projec[-fooX]/ is actually an independent chunk of code which may have different maintainers and origin. But all of them contribute to the correct execution of the project. When i need to move or copy the project i just .tar the cuis-project[-fooX] and move it around as a file. Till it is between Linux x86 there is no problem, it works with minimum effort. It it the most easy portable thing i am aware of. Moving to Linux ARM into the BeagleBoards I am aware I need to change the VM and point my startup scripts to the 32bit image. Bye Nicola <div class="moz-cite-prefix">On 12/23/21 18:46, Nicola Mingotti wrote: </div> <blockquote type="cite" cite="mid:857d9aa6-85a0-06f1-7d77-1492f0d718ba@gmail.com"> Hi Bernhard, yes, correct ! bye Nicola On 12/23/21 10:32, Bernhard Pieber via Cuis-dev wrote: <blockquote type="cite">Hi Nicola, Thanks for sharing your way of working. IIUC, your images all live in a Cuis-Smalltalk-Dev folder, either inside a cuis-project-foo*/Cuis-Smalltalk-Dev or cuis-project/Cuis-Smalltalk-Dev, right? Cheers, Bernhard <blockquote type="cite">Am 23.12.2021 um 10:27 schrieb Nicola Mingotti via Cuis-dev <a class="moz-txt-link-rfc2396E" href="mailto:cuis-dev@lists.cuis.st"><cuis-dev@lists.cuis.st></a>: hi Bernhard, I add my 2 cents experience. This is the way i found to keep things organized. for each cuis program i want to write, i mean a program i want to use on the long run i do: 1. $> mkdir cuis-project-foo1 2. $> cd cuis-project-foo1 3. $> put the VM tar file here and uncompress it here 4. $> git clone Cuis-Smalltalk-Dev *] disadvantage: it will take space on your disk and i will not be in sync with Cuis evolution. *] advantage. You can be sure your program will be always working once the test phase is over. Then, I keep a directory 'cuis-project' whithout a project name. There is where i test stuff, upgrade Cuis quite often. I work in 'cuis-project' most of the time. bye Nicola On 12/22/21 11:42, Bernhard Pieber via Cuis-dev wrote: <blockquote type="cite">Hi Juan, Thanks for the clarification. Makes sense. Cheers, Bernhard <blockquote type="cite">Am 21.12.2021 um 16:51 schrieb Juan Vuletich via Cuis-dev <a class="moz-txt-link-rfc2396E" href="mailto:cuis-dev@lists.cuis.st"><cuis-dev@lists.cuis.st></a>: Hi Bernhard, On 12/21/2021 5:53 AM, Bernhard Pieber via Cuis-dev wrote: <blockquote type="cite">Hi Juan, Thank you for the fast response. Now the shell scripts work as intended. One thing I am still unsure about: Where do you put the VM and where the working images, in MyProject or in Cuis-Smalltalk-Dev? If in Cuis-Smalltalk-Dev the Git repository gets dirty because of various files that get created, e.g. ThePig.txt. </blockquote> I put the VM at MyProject, and sometimes save images in Cuis-Smalltalk-Dev. I don't have a defined process for removing unneeded files. Maybe a couple of additional shell scripts could be of use. <blockquote type="cite">I guess the project specific packages would go into a subdirectory of MyProject like Cuis-Smalltalk-MyProject, which would be a Git repository, right? </blockquote> Yes. That is the best way to keep them organized. <blockquote type="cite">If you work on different projects, would you clone all package repositories for each of them? </blockquote> This is matter of personal preference. I usually use a single main folder. But if I was maintaining an end user application, I'd give it its own Cuis setup, to do updates to Cuis only when I'm willing to fix any possible breaking. <blockquote type="cite">Cheers, Bernhard </blockquote> Cheers, -- Juan Vuletich <a class="moz-txt-link-abbreviated" href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a> <a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a> <a class="moz-txt-link-freetext" href="https://github.com/jvuletich">https://github.com/jvuletich</a> <a class="moz-txt-link-freetext" href="https://www.researchgate.net/profile/Juan-Vuletich">https://www.researchgate.net/profile/Juan-Vuletich</a> <a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a> <a class="moz-txt-link-freetext" href="https://independent.academia.edu/JuanVuletich">https://independent.academia.edu/JuanVuletich</a> @JuanVuletich -- Cuis-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Cuis-dev@lists.cuis.st">Cuis-dev@lists.cuis.st</a> <a class="moz-txt-link-freetext" href="https://lists.cuis.st/mailman/listinfo/cuis-dev">https://lists.cuis.st/mailman/listinfo/cuis-dev</a> </blockquote> </blockquote> -- Cuis-dev mailing list <a class="moz-txt-link-abbreviated" href="mailto:Cuis-dev@lists.cuis.st">Cuis-dev@lists.cuis.st</a> <a class="moz-txt-link-freetext" href="https://lists.cuis.st/mailman/listinfo/cuis-dev">https://lists.cuis.st/mailman/listinfo/cuis-dev</a> </blockquote> </blockquote> </blockquote> </body> </html>