-
Notifications
You must be signed in to change notification settings - Fork 97
fork setup work to be done #16
Comments
Any ideas on release infrastructure? |
@evanlucas probably target a much smaller array so as to make it somewhat feasible, e.g. macOS 64, Ubuntu Linux, Windows 64. Not sure if it is possible to use travis for the first two, maybe? |
It should be, yes. I just excluded macOS from the Travis matrix because our builds take a looong time and there are generally fewer VMs available – feel free to experiment, tho :) |
Understandable, but I'd love to see more cross-platform support, not less :) I've set up ayo on my personal buildbot cluster to make unofficial builds. Here you can grab one for FreeBSD/amd64! OpenBSD currently fails with |
Hmmm yeah, I do remember something about compiling on OpenBSD I think. You may want to ask that on the Node issue tracker for now if you are comfortable with doing so. |
Sorry for stupid question. But node symlink would conflict with existing nodejs installation? I want to keep on my pc both ayo and nodejs |
@mememaestro you might want to use a version manager like asdf to switch between different versions and forks of node, as well as other languages. (But honestly I haven't found that necessary anymore, I just use the latest and greatest all the time.) |
@myfreeweb thank you =) |
@mememaestro Not necessarily, the symlink could just be removed or there could be an option to not have it installed from the installer. I think io.js did the latter option too however I am very much not familiar with msi or pkg installer manifests. |
@Fishrock123 that's great |
Here's a couple things off the top of my head. I'm certainly willing to help do some guidance on any but I have limited experience in some of these areas. Digging though the commits back to January 2015 in the related files folders will surly turn up related reference-able commits for the io.js days.
Vcbuild.bat
build/ayo.exe
.ayo
and anode
symlink.ayo
(and possibly anode
symlink.)... more to be added
The text was updated successfully, but these errors were encountered: