Adding Bower for javascript package manager

[alefbt]

Bower is grate way to get manage javascript packages.
I believe that will be easier just write in command line "bower install"
instead searching the component on internet

You can see examples @ http://bower.io/

[dpocock]

I am trying to ensure that JSCommunicator can be packaged on platforms like Debian and Ubuntu

This means that the preferred way to install and minify the code can only depend on tools that exist in Debian. bower is not currently included in Debian, http://packages.debian.org/bower does not show anything. There are similar problems with grunt.

However, I am happy to include the artifacts for people who want to use bower, can you just tweak your pull request so that the documentation suggests that bower is an optional tool rather than the only way to install?

[alefbt]

bower is package of NPM (node js)

I have debian and it works :-)

to install bower you need node.js/ npm ( https://packages.debian.org/npm)

$ apt-get install nodejs npm
$ npm install -g bower

On Fri, Aug 15, 2014 at 11:12 AM, Daniel Pocock [email protected]
wrote:

I am trying to ensure that JSCommunicator can be packaged on platforms
like Debian and Ubuntu

This means that the preferred way to install and minify the code can only
depend on tools that exist in Debian. bower is not currently included in
Debian, http://packages.debian.org/bower does not show anything. There
are similar problems with grunt.

However, I am happy to include the artifacts for people who want to use
bower, can you just tweak your pull request so that the documentation
suggests that bower is an optional tool rather than the only way to install?

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

Regards,
Yehuda Korotkin

http://www.korotkin.co.il/

web www.korotkin.co.il

mobile +972 (50) 414-6444

email [email protected]

[dpocock]

I understand this works on Debian

However, we have a rule that when we build official Debian packages, we actually compile them on a machine without any network connection. It can not download any Node packages onto the machine, it can only use tools that exist in existing Debian packages. This is how we make sure the full set of packages in Debian can be reproduced even if the version of some package in NPM goes away or changes.

[alefbt]

I see... i that case you right.

However, i think it's same dependancy issue like JQuery / ArbiterJS

On Fri, Aug 15, 2014 at 11:31 AM, Daniel Pocock [email protected]
wrote:

I understand this works on Debian

However, we have a rule that when we build official Debian packages, we
actually compile them on a machine without any network connection. It can
not download any Node packages onto the machine, it can only use tools that
exist in existing Debian packages. This is how we make sure the full set of
packages in Debian can be reproduced even if the version of some package in
NPM goes away or changes.

—
Reply to this email directly or view it on GitHub
#33 (comment)
.

Regards,
Yehuda Korotkin

http://www.korotkin.co.il/

web www.korotkin.co.il

mobile +972 (50) 414-6444

email [email protected]

[dpocock]

JQuery is available as a Debian package:
http://packages.debian.org/libjs-jquery

I made packages of ArbiterJS and jquery-i18n-properties so they would be official packages too, so the entire set of dependencies is available in Debian.