8000 fork setup work to be done · Issue #16 · ayojs/ayo · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Aug 31, 2018. It is now read-only.
This repository was archived by the owner on Aug 31, 2018. It is now read-only.

fork setup work to be done #16

Open

Description

@Fishrock123

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.

... more to be added

Activity

  1. evanlucas commented on Aug 24, 2017

    @evanlucas
    Contributor

    Any ideas on release infrastructure?

  2. Fishrock123 commented on Aug 24, 2017

    @Fishrock123
    ContributorAuthor

    @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?

  3. addaleax commented on Aug 24, 2017

    @addaleax
    Contributor

    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 :)

  4. valpackett commented on Aug 26, 2017

    @valpackett

    target a much smaller array so as to make it somewhat feasible

    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 ../deps/v8/src/trap-handler/trap-handler.h:68:8: error: thread-local storage is not supported for the current target :(

  5. Fishrock123 commented on Aug 26, 2017

    @Fishrock123
    ContributorAuthor

    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.

  6. valpackett commented on Aug 27, 2017

    @valpackett

    @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.)

  7. Fishrock123 commented on Aug 27, 2017

    @Fishrock123
    ContributorAuthor

    @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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0