Search Criteria
Package Details: freetube 0.22.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/freetube.git (read-only, click to copy) |
---|---|
Package Base: | freetube |
Description: | An open source desktop YouTube player built with privacy in mind. |
Upstream URL: | https://freetubeapp.io |
Licenses: | AGPL3 |
Submitter: | picokan |
Maintainer: | picokan |
Last Packager: | picokan |
Votes: | 75 |
Popularity: | 3.81 |
First Submitted: | 2020-10-02 22:19 (UTC) |
Last Updated: | 2024-12-13 08:37 (UTC) |
Dependencies (3)
- electron32 (electron32-binAUR)
- nodejs (nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron, nodejs-lts-jod) (make)
- yarn (yarn-pnpm-corepackAUR, corepackerAUR, yarn-berryAUR) (make)
Latest Comments
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 Next › Last »
picokan commented on 2021-04-26 09:34 (UTC)
@Renfield Compilation is failing on my machine even when compiling manually. This looks like it's a bug from the program itself, I'll try contacting the developer.
Renfield commented on 2021-04-25 14:01 (UTC)
I'm getting a lot of errors with this package. Here are the first of them:
je-vv commented on 2021-03-31 00:08 (UTC)
@picokan, could you please use
--cache "${srcdir}/npm-cache"
on every npm command, so that the FS doesn't get polluted when building? Thanks !alium commented on 2021-03-30 08:09 (UTC)
you can´t remove system´s electron from PKGBUILD and after call system´s electron to run freetube ;-)
users must install it or you should remove call electron at start ;-)
AndyRTR commented on 2021-03-20 10:45 (UTC)
'electron' runtime dependency is missing. Freetube fails to start if it's not installed.
picokan commented on 2021-03-15 19:51 (UTC)
@marcih Looking at it again, I see that the
npm ERR! cc: error: unrecognized command-line option ‘-m64’
indicates that, for whatever reason, electron's trying to build an x86_64 binary, which won't work on your aarch64 cpu. I'm very curious, but I don't have a cpu to test if this also fails on building from the git repo. I don't know why it wouldn't work using the PKGBUILD, I don't think I changed anything that would force an x64 build.marcih commented on 2021-03-14 14:14 (UTC) (edited on 2021-03-14 14:15 (UTC) by marcih)
@picokan Thanks for the update! As for my build failure, I have made no changes to your PKGBUILD. I tried clean building 0.12.0-2 just now with the same result:
picokan commented on 2021-03-13 19:31 (UTC) (edited on 2021-03-13 19:31 (UTC) by picokan)
@marcih Thank you for all of the information. Unfortunately, I don't know what's causing
sh -c node-gyp rebuild
. If you made changes to the PKGBUILD to fix some of my errors you may have accidentally written something that leads to that error. As for the sed command, the purpose was to have the freetube package use the system electron if available, and I thought that sed was necessary as I saw it being used on one of the packages mentioned here. After re-reading it and a bit of testing, I've changed the way it's done to something that won't stop working as intended as soon as Freetube changes it's target electron version or the system electron package is updated. Lastly, since this is already using makepkg, I don't think telling makepkg to make a pacman package of the pacman package electron made will work, but I haven't tried. The rest of the recommended changes have been applied, thank you to all who helped me.ZorinArch commented on 2021-03-08 09:10 (UTC)
update line 15 to
source=(https://github.com/FreeTubeApp/FreeTube/archive/v$pkgver-beta.tar.gz
marcih commented on 2021-03-07 16:00 (UTC)
Again, FYI, freetube has moved to electron 12, making line 23 of the PKGBUILD obsolete - in fact: a) freetube hasn't used electron v11.1.0 since 0.10.0; b) the regex itself is written wrong, the comma should be after the double quotes.
I don't know what the reasoning was to removing the build dependency on electron and whether it is still necessary, but if you want to keep it removed then line 23 ought to be:
sed -i 's@"electron": "^12.0.0",@@g' "$srcdir/$_pkgname-$pkgver-beta/package.json"
Also, question: since the build system can output what seems to be a pacman package directly (see "package-only-necessary.diff"), can we not somehow use that?
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 Next › Last »