Package Details: boostnote 0.8.16-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: 29
Popularity: 2.330045
First Submitted: 2016-04-11 13:01
Last Updated: 2017-10-28 15:28

Latest Comments

clone1612 commented on 2017-10-29 07:33

@zerophase Thanks for the comment. This warning can safely be ignored as the only files affected are package.json files from the individual node modules (e.g. /usr/lib/boostnote/node_modules/ua-parser-js/package.json) which are never used once packaged. However I will look into it to see if the warning can be avoided.

EDIT: Looking at it seems to be npm itself adding these absolute paths even though it doesn't use them. No option to avoid it.

zerophase commented on 2017-10-28 19:16

I'm getting WARNING: Package contains reference to $srcdir when building.

jcstryker commented on 2017-10-09 17:39


Ah that makes sense. I went ahead and blocked it anyway, but it is nice to know its purpose. Thanks for your work.

clone1612 commented on 2017-10-09 16:15

@jcstryker Thanks for the heads up. I verified it and no, it's not analytics related. It's for the bottom notification area which currently shows 'Sync Boostnote data across devices'. They send a request which return a JSON file containing the message that should be shown.

jcstryker commented on 2017-10-09 16:06


I am still getting a connection to on starting the app. Is this analytics related?

clone1612 commented on 2017-10-09 12:53

Fully removed analytics again. People keep having problems with it (e.g. and it's more privacy friendly this way. Much smaller package size is also a bonus.

clone1612 commented on 2017-08-10 15:45

If you have any problems with preferences being reset, please follow the instructions in This release contains a bug that will be fixed when they release a new version (in the coming days) but that post contains a work-around.

EDIT: Problems should be fixed with v0.8.14

clone1612 commented on 2017-07-29 07:12

Updated to v0.8.12, thanks for the advice @NicoHood. For now I've just set tracking to false by default, like you mentioned, while I look at a clean way of removing all analytics (since they changed a bit since my previous removal patch). Should be possible but do not worry even without the removal tracking is disabled by default :)

EDIT: Removed amazon analytics once again, turned out to be easier then first expected :)
If any issues arise feel free to say so and I will look into them.

NicoHood commented on 2017-07-22 06:57

Thanks for the patch!
For the next version:

in the next version you could patch browser/main/lib/ConfigManager.js to set the tracking to false by default. I think in long term it would be complicated to fully remove it. But if you can fully remove it, that'd be better :)

clone1612 commented on 2017-07-20 06:58

@NicoHood More details in this pull request:

Pushed a new package release. Found a way around the npm issue so moved back to good old npm. Also removed all of their amazon analytics, thereby also fixing the problem mentioned by @vczm. So no more analytics present which also had a great effect on the package size.

NicoHood commented on 2017-07-20 05:38

They added spy functions to boostnote? Is there any details about that? It seems I will not use Boostnote anymore with those functions.

@clone1612: We can change the source code, its GPL3. No need to ask any maker.

clone1612 commented on 2017-07-19 20:50

@vczm That's not an error I can fix. They have added amazon analytics (which are those requests) but they only add the correct key when they package for distribution (so not provided in the source code used to build the package). Unless they provide their analytics id the requests (send by the program, not something I added) will fail.

In theory the analytics could be removed but that would be really changing the source code and I have no idea if the makers would agree to that.

EDIT: Trying to get in touch with them, will see how it goes. Even if its fixed though the requests will still be send (it's their analytics) however they will no longer fail. But working on a solution.

vczm commented on 2017-07-19 20:32

Still not fixed:
Why do you need to send these requests?

clone1612 commented on 2017-07-19 19:04

@NicoHood I received a bug report that installations were failing due to an npm error. Failures could be reproduced on my two systems, both with a normal attempt to install and a clean chroot. Sadly I had a bit less time in the past days so this is a (dirty) temporary fix while I look for a definitive solution to the issue, which seems to have appeared with a recent npm update. Will look into that and move back to npm if a fix is found, but for now the focus was on making it possible to install once again. Sorry for the inconvenience.

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.

gromain commented on 2017-04-05 07:33

@clone1612, can you update the PKGBUILD here?

Also, I agree with @NicoHood concerning the proper package build.

NicoHood commented on 2017-04-03 17:06

Can anyone provide a PKGBUILD which builds the package using npm and not with extracting the debian package? I could possibly move this package to community ones a convenient way to package it was found.

Contribute here:

clone1612 commented on 2017-04-03 14:54

Currently even at version 0.8.7, an update would be appreciated. Installation of this version possible with and a `makepkg -si` install like @mnciitbhu first mentioned.

gerson commented on 2017-04-03 02:14

Thanks @mnciitbhu!! The initial submitter does not seem interested in keeping this updated. Could someone else take over? I'm new to Manjaro/Arch, so I don't know what are the proper AUR rules.

mnciitbhu commented on 2017-04-02 18:51

For version 0.8.6, download this PKGBUILD File : and do `makepkg -si` to install.

alexi246 commented on 2017-02-26 07:50

Please update :)

gromain commented on 2017-02-13 14:33

Version 0.8.5 is now available, please update.

sarcokiller commented on 2017-01-20 12:32

version 0.82 is now available

chmue commented on 2016-12-27 14:41

There is a mismatch in .SRCINFO since the update to the latest version (0.6.1-1 -> 0.7.1-1). Could you look into this? I guess you just have to update .SRCINFO to the newest version. Thank you very much!