Skip to content

Commit

Permalink
README: add snap as an installation option.
Browse files Browse the repository at this point in the history
  • Loading branch information
@ppd @whitequark
ppd authored and whitequark committed Jan 23, 2020
1 parent 2dcd81d commit 72bc71c
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions README.md
View file
Expand Up @@ -30,6 +30,20 @@ the SolveSpace maintainers for each stable release.

[rel]: https://github.com/solvespace/solvespace/releases

### Via Snap Store

Builds from master are automatically released to the `edge` channel in the Snap Store. Those packages contain the latest improvements, but receive less testing than release builds.

Future official releases will appear in the `stable` channel.

[![Get it from the Snap Store](https://snapcraft.io/static/images/badges/en/snap-store-black.svg)](https://snapcraft.io/solvespace)

Or install from a terminal:

```
snap install --edge solvespace
```

### Via third-party binary packages

_Third-party_ nightly binary packages for Debian and Ubuntu are available
Expand Down

7 comments on commit 72bc71c

@whitequark
Copy link
Contributor

@whitequark whitequark commented on 72bc71c Jan 23, 2020 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ppd1990 OK, failing the CI for ~50% of builds is unacceptable. I restarted the build manually here and it failed the second time, building snaps of course. Unless a solution is found I'll have to revert this.

@ppd
Copy link
Member Author

@ppd ppd commented on 72bc71c Jan 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm. Very unfortunate. We need a way to ignore previously started remote-builds. I'll investigate the options.

@ppd
Copy link
Member Author

@ppd ppd commented on 72bc71c Jan 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reading through snapcraft's code, it seems like it wants to either recover or clean a build on launchpad. So no starting parallel builds without killing currently running ones.

Also no cancelling previous builds without user input (or hacky yes n | ...) ; there is no command option to do so. 🤦‍♂️

@whitequark
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ouch.

@ppd
Copy link
Member Author

@ppd ppd commented on 72bc71c Jan 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can do builds with docker as mentioned in the issue. At least for amd64 it should be quite simple

@whitequark
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe open a feature request?

@ppd
Copy link
Member Author

@ppd ppd commented on 72bc71c Jan 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will. But I think the "one build at a time" constraint is here to stay and that means we'll always have problems with quick sequential commits or builds for PRs.

Please sign in to comment.