Ahh Yes! You can do nice release on the GH. We are doing such based on TAG. I'm putting in the description links to the release [1]
[1] https://github.com/prominic/Moonshine-IDE/releases 2018-01-24 20:58 GMT+01:00 Alex Harui <[email protected]>: > The NPM install name is defined in package.json. > > The -bin-js package is JS only, no SWF support. It's package name is > 'royale'. Turns out there is already a 'royale' out there, so I've > already changed it to 'apache-royale' in the nightly builds and for the > next release. Technically, we shouldn't NPM publish this package with its > new name until we've officially released the source file with the new name > in it, but also, technically, binary packages are not official releases of > the ASF. I think any individual could publish a nightly as apache-royale, > but I'm not sure it is worth it. Folks can just use npm install <url to > the package> as I instructed upthread. If someone wants to put that > package some place that isn't mirrored, they can do that as well. We > could put it on the CI server, for example. > > The -bin-js-swf package contains SWF support and thus it contains a .js > file that downloads the Adobe SDKs. It looks like that .js file needs > fixing so no matter where or how you get at that package, it will throw an > error on installation. Someone needs to take the time to fix that .js > file and then we can discuss whether to publish it or not. > > IMO, we should just tell folks who ask to install the 'royale' package via > the mirrors or maybe put a copy up on another server. Does GH have a > releases folder or something like that? I hope to start the 0.9.1 release > in 10 to 14 days. > > Thoughts? > -Alex > > On 1/24/18, 11:44 AM, "Piotr Zarzycki" <[email protected]> wrote: > > >I just wanted to say that we shouldn't loose opportunity to show that > >release. If npm is not working let's provide simple urls on the website. > > > >2018-01-24 19:59 GMT+01:00 Piotr Zarzycki <[email protected]>: > > > >> If npm is broken and it's require fix in the source I understand. What's > >> with second option ? For this release we could provide on the website at > >> least links. > >> > >> Thanks, > >> Piotr > >> > >> 2018-01-24 19:33 GMT+01:00 Alex Harui <[email protected]>: > >> > >>> I'm not sure how to fix the npm issues without changing a source file. > >>> Any ideas? > >>> > >>> Get Outlook for > >>>Android<https://na01.safelinks.protection.outlook. > com/?url=https%3A%2F%2 > >>>Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com% > 7Cdec5bceb963f427bfce > >>>308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C6365241990598 > >>>71558&sdata=Ck0YuGPpWIOI8OtZcmmk5bSdqlkdf209IgzgXGZhvL4%3D&reserved=0> > >>> > >>> ________________________________ > >>> From: Piotr Zarzycki <[email protected]> > >>> Sent: Wednesday, January 24, 2018 10:17:12 AM > >>> To: [email protected] > >>> Subject: Re: Cannot install royale-swf from npm > >>> > >>> Alex, > >>> > >>> Can we republish once again everything ? If not can we upload binaries > >>>to > >>> Apache mirrors[1] as we had this with Flex ? > >>> > >>> [1] > >>> https://na01.safelinks.protection.outlook.com/?url=http%3A% > >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Fflex%2F4.16.1% > >>> 2Fbinaries%2Fapache-flex-sdk-4.16.1-bin.zip&data=02%7C01% > >>> 7Caharui%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa > >>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636524146406190877& > >>> sdata=KS5MwWOTANwoaf9iihN2CBWFtTfOgUKfNBRMr5qb%2Blc%3D&reserved=0 > >>> > >>> Thanks, > >>> Piotr > >>> > >>> > >>> 2018-01-24 19:11 GMT+01:00 Alex Harui <[email protected]>: > >>> > >>> > Bummer. Maybe nobody actually tested the royale-swf package. I only > >>> > tested the royale package which we did not publish due to collision > >>>with > >>> > another royale package out there. In the next release we will name > >>>the > >>> > packages apache-royale and apache-royale-swf. > >>> > > >>> > Do you have time to try to fix it? Running "ant release" builds > >>> packages > >>> > in the "out" folder. Or you can commit changes, and wait for the > >>> nightly > >>> > build. In theory, instead of running "npm install royale-swf", you > >>>can > >>> > swap in the path to your out folder or the url to the nightly build > >>> > package instead of "royale-swf". > >>> > > >>> > If you don't really need SWF support, you can try npm on the released > >>> > bin-js.tar.gz file. Go get the link to the package on the mirrors by > >>> > hitting this link: > >>> > > >>> > https://na01.safelinks.protection.outlook.com/?url=http%3A% > >>> 2F%2Fwww.apache.org%2Fdyn%2Fcloser.lua%2Froyale%2F0.9.0% > >>> 2F&data=02%7C01%7Caharui%40adobe.com%7C1faec7dcd0424ee4 > >>> 086108d56356b4c6%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > >>> 7C636524146406190877&sdata=%2FFYClpVHC44aEj%2FdYXDGvfqwQq%2F > >>> 2nxga4gg309Oh48I%3D&reserved=0 > >>> > binaries/apache-royale-0. > >>> > 9.0-bin-js.tar.gz > >>> > > >>> > Then try 'npm install -g <link to mirrored package>'. > >>> > > >>> > It seemed to work for me. > >>> > > >>> > HTH, > >>> > -Alex > >>> > > >>> > > >>> > On 1/24/18, 9:21 AM, "Josh Tynjala" <[email protected]> wrote: > >>> > > >>> > >I get the following console output when I run `npm install -g > >>> royale-swf` > >>> > > > >>> > >https://na01.safelinks.protection.outlook.com/?url= > >>> > https%3A%2F%2Fpaste.apa > >>> > >che.org%2FxA7e&data=02%7C01%7Caharui%40adobe.com% > >>> > 7C10eefaebf4d64e560dc708d > >>> > >5634ee373%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > >>> > 7C636524112827939628& > >>> > >sdata=BsIWbDYgwtLmEWFmTte7MT8Keb0orwvHRhx47rCVgjw%3D&reserved=0 > >>> > > > >>> > >It appears that royale-asjs is missing from the path when running > >>>the > >>> > >`npm/dependencies/download_dependencies.js` script. > >>> > > > >>> > >- Josh > >>> > > >>> > > >>> > >>> > >>> -- > >>> > >>> Piotr Zarzycki > >>> > >>> Patreon: *https://na01.safelinks.protection.outlook.com/?url=https% > >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu > >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7 > >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877& > >>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0 > >>> <https://na01.safelinks.protection.outlook.com/?url=https% > >>> 3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharu > >>> i%40adobe.com%7C1faec7dcd0424ee4086108d56356b4c6%7Cfa7b1b5a7 > >>> b34438794aed2c178decee1%7C0%7C0%7C636524146406190877& > >>> sdata=SXs8ff3Qz42jBB7vq%2FNOSsg%2BBj67rGgUlLvhtllA13c%3D&reserved=0>* > >>> > >> > >> > >> > >> -- > >> > >> Piotr Zarzycki > >> > >> Patreon: > >>*https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.pat > >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com > %7Cdec5bceb963f > >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C6365241 > >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN > 90aC%2BAyOhGtLI%3D&reserv > >>ed=0 > >> > >><https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.pat > >>reon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com > %7Cdec5bceb963f > >>427bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C6365241 > >>99059871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN > 90aC%2BAyOhGtLI%3D&reserv > >>ed=0>* > >> > > > > > > > >-- > > > >Piotr Zarzycki > > > >Patreon: > >*https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.patr > >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com% > 7Cdec5bceb963f42 > >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C6365241990 > >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN > 90aC%2BAyOhGtLI%3D&reserved=0 > ><https://na01.safelinks.protection.outlook.com/?url= > https%3A%2F%2Fwww.patr > >eon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com% > 7Cdec5bceb963f42 > >7bfce308d56362f69d%7Cfa7b1b5a7b34438794aed2c178de > cee1%7C0%7C0%7C6365241990 > >59871558&sdata=yGP2VsnYdOVA4RUMkpmMlCXzcmTClN > 90aC%2BAyOhGtLI%3D&reserved=0 > >>* > > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
