Package Details: peerflix 0.37.0-2

Git Clone URL: (read-only)
Package Base: peerflix
Description: Streaming torrent client for node.js
Upstream URL:
Licenses: MIT
Submitter: heddson
Maintainer: heddson
Last Packager: heddson
Votes: 48
Popularity: 0.406814
First Submitted: 2014-03-18 19:42
Last Updated: 2017-07-20 22:50

Latest Comments

heddson commented on 2017-07-20 22:53

I got the same issue after updating npm.. Seems to be an issue with npm 5. Got around it by adding the path to the tarball.

I'm not too keen on using the registry name with 'npm install' as young.acinonyx suggested. That would download it from the registry, instead of using the already downloaded source taball..

Updated the PKGBUILD.

damien commented on 2017-07-18 05:13

Thanks young.acinonyx, that PKGBUILD works for me.

young.acinonyx commented on 2017-07-18 00:09

I compiled this package with the following PKGBUILD and it worked:

pkgdesc="Streaming torrent client for node.js"

package() {
cd "${srcdir}/${pkgname}-${pkgver}"

install -Dm644 LICENSE -t "${pkgdir}/usr/share/licenses/${pkgname}"
npm install -g --prefix "${pkgdir}/usr" peerflix

# vim:set ts=2 sw=2 et:

heddson commented on 2017-07-17 15:57

Strange. I get the following output:

$ file /usr/lib/node_modules/peerflix
/usr/lib/node_modules/peerflix: directory

damien commented on 2017-07-17 14:56

Hi, the latest release doesn't seem to be working for me.

I believe this is the problem:

$ file /usr/lib/node_modules/peerflix
/usr/lib/node_modules/peerflix: broken symbolic link to ../../../../../src/peerflix-0.37.0

heddson commented on 2015-10-06 19:10

Hi! Yeah I saw that to.. When I run 'grep -R "$(pwd)" pkg' I get alot of hits.

The references to pwd doesn't matter, but I concur that it's not that nice to have those warnings.

I don't know how to how to hide/remove it (without using some ugly hack with sed or something).. I'll have to investigate it some more.

zopieux commented on 2015-09-23 14:03

==> WARNING: Package contains reference to $srcdir
==> WARNING: Package contains reference to $pkgdir

I'm not sure if this is an actual issue. Could you fix that in the next release if it is?

heddson commented on 2015-05-09 19:34

Yeah I see now that they broke out npm from the nodejs package. Thanks for the heads up!

backpackjoe commented on 2015-05-09 16:52

This package requires "npm" to build, after installing that packaging went fine.

Anonymous comment on 2015-02-02 19:57

0.25.2 is out

All comments