Hello, v0.11.11 has been released and this time it seems to be properly tagged on github, so you should be able to build without any issues hopefully. Thanks in advance!
Search Criteria
Package Details: boostnote 0.11.11-1
| Git Clone URL: | https://aur.archlinux.org/boostnote.git (read-only) |
|---|---|
| Package Base: | boostnote |
| Description: | Open source note-taking app for programmers |
| Upstream URL: | https://boostnote.io/ |
| Keywords: | electron productivity |
| Licenses: | |
| Submitter: | rokt33r |
| Maintainer: | clone1612 |
| Last Packager: | clone1612 |
| Votes: | 49 |
| Popularity: | 2.620259 |
| First Submitted: | 2016-04-11 13:01 |
| Last Updated: | 2018-11-17 11:28 |
Dependencies (5)
- electron (electron-wayland)
- nodejs (nodejs-git, nodejs-0.12, nodejs6-bin, nodejs-lts-boron, nodejs-lts-carbon, nodejs-lts-dubnium)
- git (git-git) (make)
- grunt-cli (make)
- npm (npm53, npm4, nodejs6-bin) (make)
Required by (0)
Sources (5)
ToKrCZ commented on 2018-11-16 17:43
SirJson commented on 2018-10-27 17:29
If someone absolutely needs to build v0.11.10 right now he can try my script:
https://github.com/SirJson/boostnote-builder
I made it because I needed Boostnote on a system without Arch Linux. The script is based on the PKGBUILD that I found here but I thought why not upgrade the version to v0.11.10 as well.
The installer will make a user local installation (everything stays in your home directory) so it shouldn't clash with any packages. But as I said only if you absolutely need the newest version right now. Using the AUR is usually the better option here.
Also there shouldn't be that much of a difference between 0.11.9 and 0.11.10.
mapcode.mind commented on 2018-10-20 19:12
Regarding the update to v0.11.10: I can't update this package until the release is tagged on the main repository (https://github.com/BoostIO/Boostnote/issues/2513).
saw that just now, the tag is still at 0.11.9.
Edit : But, why can't this package be updated? the code is sitting right there. just saying cause they have marked your issue as improvement request.
clone1612 commented on 2018-10-20 08:58
Regarding the update to v0.11.10: I can't update this package until the release is tagged on the main repository (https://github.com/BoostIO/Boostnote/issues/2513).
clone1612 commented on 2018-08-27 06:46
@phxphx Hmm, not that I know off. I've just tested it and images paste without any issue in my installation. Can you open the console (Ctrl+Shift+I) and see if an error appears when you paste an image?
phxphx commented on 2018-08-26 11:16
Just installed boostnote for the first time, I've noticed that I'm unable to paste images into a note.
Am i missing a dependency?
vczm commented on 2018-06-14 08:50
@clone1612 Sorry, my mistake. In file system I store my notes in subfolders of the Boostnote folder. In the settings, I added the subfolders manually, and it works fine.
clone1612 commented on 2018-06-14 08:28
@vczm Hmm, strange. I've tested it and the upgrade went without any issues. Is there anything visible on the Developer Tools console? Ctrl+Shift+I
vczm commented on 2018-06-14 08:23
After update to 0.11.6-1 the notes directory was reset to default. In settings I tried to add directory with my notes, but no got the expected result (message returned - No Folders).
clone1612 commented on 2018-06-13 06:04
Just an FYI on certain warnings appearing during the installation:
-
Warning about optional dependencies -> Bug in npm ignoring the --no-optional flag (https://github.com/npm/npm/issues/17633)
-
Reference to $srcdir ... -> Again unwanted behaviour in npm which saves absolute paths in the package.json file (https://github.com/npm/npm/issues/10393). These warnings can safely be ignored since package.json is not used after installation.
-
Security alerts -> Upstream issue, I'll try looking into it and fix things where possible
Pinned Comments
clone1612 commented on 2018-06-13 06:04
Just an FYI on certain warnings appearing during the installation:
Warning about optional dependencies -> Bug in npm ignoring the --no-optional flag (https://github.com/npm/npm/issues/17633)
Reference to $srcdir ... -> Again unwanted behaviour in npm which saves absolute paths in the package.json file (https://github.com/npm/npm/issues/10393). These warnings can safely be ignored since package.json is not used after installation.
Security alerts -> Upstream issue, I'll try looking into it and fix things where possible