<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 5 Apr 2017, at 22:46, Fabio Niephaus <<a href="mailto:lists@fniephaus.com" class="">lists@fniephaus.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="">On Wed, Apr 5, 2017 at 6:07 PM Ben Coman <<a href="mailto:btc@openinworld.com" class="">btc@openinworld.com</a>> wrote:<br class=""></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><br class="gmail_msg">On Wed, Apr 5, 2017 at 8:44 PM, Esteban Lorenzano <<a href="mailto:estebanlm@gmail.com" class="gmail_msg" target="_blank">estebanlm@gmail.com</a>> wrote:<br class="gmail_msg">><br class="gmail_msg">><br class="gmail_msg">> On 5 Apr 2017, at 14:34, Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" class="gmail_msg" target="_blank">nicolas.cellier.aka.nice@gmail.com</a>> wrote:<br class="gmail_msg">><br class="gmail_msg">> Hi Esteban,<br class="gmail_msg">> You mean moving more things up in opensmalltalk-vm?<br class="gmail_msg">><br class="gmail_msg">> Yes that sounds the way to go, (much more simple workflow).<br class="gmail_msg">><br class="gmail_msg">><br class="gmail_msg">> yes, what I do want is<br class="gmail_msg">> - to move and adapt:<br class="gmail_msg">> - pack-vm.sh<br class="gmail_msg">> -<span class="Apple-converted-space"> </span><a href="http://deploy-files.pharo.org-appveyor.sh/" rel="noreferrer" class="gmail_msg" target="_blank">deploy-files.pharo.org-appveyor.sh</a><br class="gmail_msg">> -<span class="Apple-converted-space"> </span><a href="http://deploy-files.pharo.org.sh/" rel="noreferrer" class="gmail_msg" target="_blank">deploy-files.pharo.org.sh</a><br class="gmail_msg">> - deploy_key.enc<br class="gmail_msg">> - deploy-key.sh<br class="gmail_msg">><br class="gmail_msg">> For your keys, it's not my expertise, but you could google something like "deploy and sign in travis secret keys"<br class="gmail_msg">><span class="Apple-converted-space"> </span><a href="https://docs.travis-ci.com/user/encryption-keys/" rel="noreferrer" class="gmail_msg" target="_blank">https://docs.travis-ci.com/user/encryption-keys/</a><br class="gmail_msg">><span class="Apple-converted-space"> </span><a href="http://stackoverflow.com/questions/9338428/using-secret-api-keys-on-travis-ci" rel="noreferrer" class="gmail_msg" target="_blank">http://stackoverflow.com/questions/9338428/using-secret-api-keys-on-travis-ci</a><br class="gmail_msg">><br class="gmail_msg">><br class="gmail_msg">> yeah, that does not work because how<span class="Apple-converted-space"> </span><a href="http://files.pharo.org/" rel="noreferrer" class="gmail_msg" target="_blank">files.pharo.org</a><span class="Apple-converted-space"> </span>is managed (not by us, so we cannot modify that part of the equation). So I need the keys… but I already made it work, so I just need to make that work also on osvm :)<br class="gmail_msg">><br class="gmail_msg">> one thing I want to know is where to put those files… maybe a subdir “pharo-deploy”? or a ./deploy/pharo? (so in the future other flavours can put their specific files there?<br class="gmail_msg"><br class="gmail_msg">Maybe "packaging" - since you may want to generate rpm, deb, snapcraft<br class="gmail_msg">packages and well as deploy those.<br class="gmail_msg"><br class="gmail_msg">Or "distribution" - since in the same way RedHat/Debian are downstream<br class="gmail_msg">distributions of Linux,<br class="gmail_msg">Squeak/Pharo/Cuis/Newspeak might be considered downstream<br class="gmail_msg">distributions of OpenSmalltalk.<br class="gmail_msg"><br class="gmail_msg">Or "dialect" - since that is how we often refer to Pharo/Squeak etc...<br class="gmail_msg"><br class="gmail_msg">But actually "deploy" probably encompasses those cases reasonably well.<br class="gmail_msg">But rather than "pharo-deploy", if located in the root folder it sould follow<br class="gmail_msg"> "build.platformXXX" pattern to be "deploy.pharo"<br class="gmail_msg"><br class="gmail_msg">./deploy/pharo versus ./deploy.pharo would maybe depend or whether in<br class="gmail_msg">future there is much common with the deploy scripts between dialects.<br class="gmail_msg"></blockquote><div class=""><br class=""></div><div class="">I'd prefer a ./deploy/ directory with a file or a subdirectory for each deployment target, e.g. ./deploy/bintray.sh and ./deploy/pharo/ (if you need to have multiple deployment scripts for pharo). Then we could have common scripts in ./deploy/common.sh or ./deploy/common/ (if necessary).</div><div class="">If we follow the build.platformXXX pattern for deployments, we eventually end up with a bunch of more directories in the root directory and that already has lots of subdirectories.</div></div></div></div></blockquote><div><br class=""></div><div>ok</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_quote"><div class=""><br class=""></div><div class="">Also, I think it'd be great if Pharo remains part of the current deployment set. But I of course understand that you might additionally deploy the vm to some other deployment target.</div></div></div></div></blockquote><div><br class=""></div><div>We have out infrastructure requirements and we need to deploy to our servers. </div><div>But I do not see why it can not be both (and I never said otherwise) :)</div><div><br class=""></div><div>Esteban</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="gmail_quote"><div class=""><br class=""></div><div class="">Fabio</div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><br class="gmail_msg"><br class="gmail_msg">btw, it might nice to have somewhere to consolidate duplication like this...<br class="gmail_msg"><br class="gmail_msg">build.win32x86/squeak.cog.v3/squeak.ico<br class="gmail_msg">build.win32x86/squeak.cog.spur/squeak.ico<br class="gmail_msg">build.win32x86/squeak.cog.spur.lowcode/squeak.ico<br class="gmail_msg">build.win32x86/squeak.stack.v3/squeak.ico<br class="gmail_msg">build.win32x86/squeak.stack.spur/squeak.ico<br class="gmail_msg">build.win32x86/pharo.cog.spur/Pharo.ico<br class="gmail_msg">build.win32x86/pharo.cog.spur.lowcode/Pharo.ico<br class="gmail_msg">build.win64x64/squeak.stack.spur/squeak.ico<br class="gmail_msg">build.win64x64/squeak.cog.spur/squeak.ico<br class="gmail_msg">build.win64x64/pharo.stack.spur/Pharo.ico<br class="gmail_msg">platforms/win32/misc/squeak.ico<br class="gmail_msg">platforms/iOS/vm/OSX/Squeak.icns<br class="gmail_msg">platforms/Mac OS/Resources/Squeak.icns<br class="gmail_msg"><br class="gmail_msg">build.linux32x86/editpharoinstall.sh<br class="gmail_msg">build.linux64x64/editpharoinstall.sh<br class="gmail_msg">build.linux32ARMv6/editpharoinstall.sh<br class="gmail_msg"><br class="gmail_msg">build.linux32x86/editnewspeakinstall.sh<br class="gmail_msg">build.linux64x64/editnewspeakinstall.sh<br class="gmail_msg">build.linux32ARMv6/editnewspeakinstall.sh<br class="gmail_msg">build.linux32ARMv7/editnewspeakinstall.sh<br class="gmail_msg"><br class="gmail_msg"><br class="gmail_msg">cheers -ben<br class="gmail_msg"><br class="gmail_msg">><br class="gmail_msg">> Esteban<br class="gmail_msg">><br class="gmail_msg">><br class="gmail_msg">> etc…<br class="gmail_msg">><br class="gmail_msg">><br class="gmail_msg">> 2017-04-05 8:27 GMT+02:00 Esteban Lorenzano <<a href="mailto:estebanlm@gmail.com" class="gmail_msg" target="_blank">estebanlm@gmail.com</a>>:<br class="gmail_msg">>><br class="gmail_msg">>><br class="gmail_msg">>> Hi guys,<br class="gmail_msg">>><br class="gmail_msg">>> I was reading the other thread this morning and I figure out I have an easy way of solve all problems (besides that damn String primitive problem that still needs to be fixed).<br class="gmail_msg">>> This is the thing:<br class="gmail_msg">>><br class="gmail_msg">>> If I can add special deploy script for Pharo (with my keys, so is not soooo cool, but is not so bad either), to deploy osvm build VMs into Pharo infrastructure, then I can<br class="gmail_msg">>><br class="gmail_msg">>> 1) use that as our “stable” builds.<br class="gmail_msg">>> 2) keep having the rest of the process unaltered, so we will keep the validation infrastructure and the nightly builds (that we call “latest”).<br class="gmail_msg">>><br class="gmail_msg">>> and then, everything will be “as it should be”.<br class="gmail_msg">>><br class="gmail_msg">>> what do you think, can I go ahead and modify that part?<br class="gmail_msg">>><br class="gmail_msg">>> Esteban<br class="gmail_msg">><br class="gmail_msg">><br class="gmail_msg">><br class="gmail_msg">></blockquote></div></div></div></blockquote></div><br class=""></body></html>