Skip to content

We should probably talk about how IUP is distributed. #3

@abonander

Description

@abonander

@dcampbell24 @thelink2012

So, Sourceforge users are fleeing en masse after finding out that SF is adding ads to software without the project owners' consent.

This is a bit of a concern since we (KISS-UI and IUP-Rust) are asking our users to go to Sourceforge and download precompiled binaries for IUP. IUP as a project is probably flying far under Sourceforge's radar since it's not big enough to make injecting malvertising worth it, but we should probably look into solutions for getting IUP binaries out there that are much more future-proof and much less sketchy.

Travis CI has Linux and OS X workers and can integrate with GitHub Releases, which means we can mirror IUP to GitHub, have Travis build binaries for those platforms in the open--the build logs are fully available as are the scripts--and then make them available for download. We could use AppVeyor for the Windows builds, it's just about as open. I've used both platforms before.

The only downside I can see is that we should talk about how we're going to support 32-bit, as all these workers are running on 64-bit OSes. We could run the builds twice with one set to 32-bit, I guess.

What do you guys think? Should we see what IUP's author is doing about this or if he even knows? Or just go ahead with this in the spirit of open-source?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions