Package Details: boostnote 0.12.1-1

Git Clone URL: (read-only)
Package Base: boostnote
Description: Open source note-taking app for programmers
Upstream URL:
Keywords: electron productivity
Licenses: GPL3
Submitter: rokt33r
Maintainer: clone1612
Last Packager: clone1612
Votes: 55
Popularity: 1.196225
First Submitted: 2016-04-11 13:01
Last Updated: 2019-07-27 09:50

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 (

  • Reference to $srcdir ... -> Again unwanted behaviour in npm which saves absolute paths in the package.json file ( 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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

NicoHood commented on 2017-07-19 16:11

Why did you switch to yarn?

clone1612 commented on 2017-06-17 15:09

Updated to 0.8.10 with a patch for the errors encountered. File size has significantly increased though, for the largest part thanks to the new amazon analytics modules. I will be however looking in the next days on ways to reduce the size, some tweaks here and there might work.

EDIT: Updated the package with an improved patch where I included a fix for the package size. Reduced size by +- 30 MiB when compared to vanilla 0.8.10.

clone1612 commented on 2017-06-12 18:32

Working on 0.8.10 but the developers seem to have done some changes which break the app when compiled from source. I have opened a bug report with them and will update when possible. The bug is that when compiled from source notes will not show, which is really a major issue.

clone1612 commented on 2017-05-30 10:16

@NicoHood Thanks again for the helpful suggestions, I will incorporate them with the next update.

NicoHood commented on 2017-05-27 21:16

@clone1612 Two more suggestions:
* Use cp -a instead of -r
* Prefix the github source with: ${pkgname}-${pkgver}.tar.gz::

Nice job, the app works perfect for me! Still waiting for them to GPG sign it so I can move it to [community].

clone1612 commented on 2017-04-08 14:55

Thanks for the helpful advice @tensor5! Incorporated it in this next package release, which fixes all warnings related to npm (save one about an advice of installing with -g), grunt and namcap. If any issues arise feel free to post it.

tensor5 commented on 2017-04-08 11:24

Hi everyone,

The new package looks good and it's working. Just a couple of cosmetic suggestions:

1. The line `cp resources/app.png ../app.png` could be removed and line 54 changed to `install -Dm644 resources/app.png "$pkgdir/usr/share/pixmaps/${pkgname}.png".

2. I use the `find` command at the end of the file to remove all the useless stuff installed by npm until I get 0 namcap warnings.

clone1612 commented on 2017-04-06 07:26

With the great help of @NicoHood a complete redesign of the way this package is build was done, with now time for a first release. With such a big overhaul bugs/errors might pop up so if you encounter any issues feel free to comment. It might ask you once for your note storage location, this due the move of the cache to a more proper location.

Package size is down by 66% and we now make use of electron provided by arch itself.

NicoHood commented on 2017-04-05 14:16

I asked tensor5 for some help. See the email below:

Hi Nico,
Building an electron app requires sometimes a little bit of black art.
Ideally it should be enough to run `npm install --production`, and then
running `electron .` inside the root of the project should to start the
app. Try that first and see if it works.
Most apps however include build scripts (usually grunt or gulp) that:

1. run build tasks (coffee, babel, etc.)

2. download a binary version of Electron and package the app with the
binary. This step is usually done with devDependencies such as
electron-packager and electron-prebuilt + some tasks in gulp or grunt
that moves files around.

In order to package your app with Arch's electron you should eliminate
step 2 above, and it usually involves patching package.json and/or the
build scripts. Start from package.json, read the "scripts" section and
see what it does during the build process. Then read the relevant build
scripts, and remove the parts that involve downloading the binary
electron. At the end your package should consist of the project root
with the transformation done grunt or gulp.

I install apps in /usr/lib/<name of app> and I launch it through a
wrapper script called <name of app>.js that I install in /usr/bin/<name
of app>.

Check the following packages for reference:

If you still have troubles, I can take a look at the specific package
next weekend.


clone1612 commented on 2017-04-05 07:53

@gromain Updated the PKGBUILD. Also looking at a more proper build and will try to contribute to the issue opened by @NicoHood.