Packaging and name clash

[Lubomir Rintel]

Hi,

Some time ago I made a RPM package og node.js and submitted it for
inclusion in Fedora operating system (a Linux distribution):
https://bugzilla.redhat.com/show_bug.cgi?id=634911

During the review, the reviewer pointed out that the name of the
binary (and the package, been renamed from node to nodejs since then)
clashes with an existing package (a "Simple node front end, modelled
after the node shells of TheNet and G8BPQ nodes"); can be found here:
ftp://ftp.hes.iki.fi/pub/ham/linux/ax25/

The package's binary is called /usr/sbin/node; and though it does not
directly clash with node.js's /usr/bin/node; it's easily confused when
called without a path: "node".

I'm wondering if at this point it would be possible to rename the
binary (e.g. to "nodejs"), or someone suggests a better solution to
the problem?

Thanks in advance,
Lubo

[Ryan Dahl]

I want Node to have the executable name 'node'.

You can contact the author of the other package and see if they'll
change their name.

[Rik Arends]

Hi Everybody,

We just released a new Canvas api for NodeJS to play with:

https://github.com/ajaxorg/node-o3-canvas

Blog article with demo video of running/debugging the thing in cloud9 here:

http://ajaxorg.posterous.com/canvas-api-for-nodejs

The api is not yet fully complete, and we are working right now to add the missing bits like font-rendering and gradient support.

Though it should be good enough now to render some charts and play around with it.

Best

Rik Arends

Ajax.org / Cloud9

[Jérémy Lal]

Hi,
you'll read the same discussion with debian nodejs package at :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597571

I hope that helps,
J�r�my.

[Isaac Schlueter]

> On 04/11/2010 15:42, Ryan Dahl wrote:
>> I want Node to have the executable name 'node'.

+1.

--i

[Dominic Tarr]

to be fair, isn't naming in linux package managers a matter of first in first served?

 

--
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com.
To unsubscribe from this group, send email to nodejs+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.

[Micheil Smith]

Do we really need node to be in a linux package manager?

Yours,
Micheil Smith
--
BrandedCode.com

[Alan Gutierrez]

Package managers solve a problem. They are not going out of fashion any
time soon.

The RPMs and debs I build install node at /usr/bin/node.

--
Alan Gutierrez

[Gerad Suyderhoud]

Hmm... package managers ease upgrading.  How do people upgrade node on their servers now? Re-download and recompile?

--

[Isaac Schlueter]

On Tue, Nov 9, 2010 at 18:20, Gerad Suyderhoud <ger...@gmail.com> wrote:
> Hmm... package managers ease upgrading.  How do people upgrade node on their
> servers now? Re-download and recompile?

nave use latest

(So, yes, but perhaps with a script to make it easier ;)

--i

[Ryan Gahl]

bleeding edge:

--

git pull

make distclean

./configure

make && make install && make test

tagged stable versions:

--

nvm install v0.2.4 (or other tagname)

[Fedor Indutny]

What do you think about module, that will automate this process?

2010/11/10 Ryan Gahl <ryan...@gmail.com>

--
Fedor Indutny

[Isaac Schlueter]

Fedor:

There are two: nave and nvm.

--i

[Fedor Indutny]

Isaac:

fail :(

2010/11/10 Isaac Schlueter <i...@izs.me>

--
Fedor Indutny

[Oleg "Sannis" Efimov]

I've builded RPM's for both Node v0.2.4 and v0.3.x. If this good for
you, look at http://bit.ly/nodejs_repos and http://bit.ly/nodejs3_repos.
Also there are DEB for v0.2.4 and I can build them for v0.3.x if they
needed.

On 10 ноя, 12:24, Fedor Indutny <fedor.indu...@gmail.com> wrote:
> Isaac:
> fail :(
>
> 2010/11/10 Isaac Schlueter <i...@izs.me>
>
>
>
> > Fedor:
>
> > There are two: nave and nvm.
>
> > --i
>

> > On Tue, Nov 9, 2010 at 18:46, Fedor Indutny <fedor.indu...@gmail.com>

> > wrote:
> > > What do you think about module, that will automate this process?
>

> > > 2010/11/10 Ryan Gahl <ryan.g...@gmail.com>

> > a...@prettyrobots.com>

> > >>> > wrote:
>
> > >>> >> Package managers solve a problem. They are not going out of fashion
> > >>> >> any
> > >>> >> time soon.
>
> > >>> >> The RPMs and debs I build install node at /usr/bin/node.
>
> > >>> >> --
> > >>> >> Alan Gutierrez
>
> > >>> >> On 11/8/10 3:48 AM, Micheil Smith wrote:
>
> > >>> >>> Do we really need node to be in a linux package manager?
>
> > >>> >>> Yours,
> > >>> >>> Micheil Smith
>
> > >>> >> --
> > >>> >> You received this message because you are subscribed to the Google
> > >>> >> Groups
> > >>> >> "nodejs" group.
> > >>> >> To post to this group, send email to nod...@googlegroups.com.
> > >>> >> To unsubscribe from this group, send email to

> > >>> >> nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .

> > >>> >> For more options, visit this group at
> > >>> >>http://groups.google.com/group/nodejs?hl=en.
>
> > >>> > --
> > >>> > You received this message because you are subscribed to the Google
> > >>> > Groups
> > >>> > "nodejs" group.
> > >>> > To post to this group, send email to nod...@googlegroups.com.
> > >>> > To unsubscribe from this group, send email to

> > >>> > nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .

> > >>> > For more options, visit this group at
> > >>> >http://groups.google.com/group/nodejs?hl=en.
>
> > >>> --
> > >>> You received this message because you are subscribed to the Google
> > Groups
> > >>> "nodejs" group.
> > >>> To post to this group, send email to nod...@googlegroups.com.
> > >>> To unsubscribe from this group, send email to

> > >>> nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .

> > >>> For more options, visit this group at
> > >>>http://groups.google.com/group/nodejs?hl=en.
>
> > >> --
> > >> You received this message because you are subscribed to the Google
> > Groups
> > >> "nodejs" group.
> > >> To post to this group, send email to nod...@googlegroups.com.
> > >> To unsubscribe from this group, send email to

> > >> nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .

> > >> For more options, visit this group at
> > >>http://groups.google.com/group/nodejs?hl=en.
>
> > > --
> > > Fedor Indutny
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "nodejs" group.
> > > To post to this group, send email to nod...@googlegroups.com.
> > > To unsubscribe from this group, send email to

> > > nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .

> > > For more options, visit this group at
> > >http://groups.google.com/group/nodejs?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "nodejs" group.
> > To post to this group, send email to nod...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > nodejs+un...@googlegroups.com<nodejs%2Bunsu...@googlegroups.com>
> > .

[Ryan Gahl]

On Wed, Nov 10, 2010 at 3:24 AM, Fedor Indutny <fedor....@gmail.com> wrote:

Isaac:

fail :(

Fedor: 

fail :(

Not sure what you want dude. It sounds like you're asking for a fix to a problem that isn't really a problem.

[Sami Samhuri]

On Nov 9, 6:20 pm, Gerad Suyderhoud <ger...@gmail.com> wrote:
> Hmm... package managers ease upgrading.  How do people upgrade node on their
> servers now? Re-download and recompile?
>

We use chef[1] and have a cookbook for node[2]. To upgrade we modify
attributes[3] (or set those attributes for machines w/ a certain role)
and then kick back and wait for the next chef-client run (every 1/2
hour for us). Or we run chef-client manually if we want to upgrade
immediately.

[1] http://www.opscode.com/chef/
[2] https://github.com/samsonjs/cookbooks/tree/master/node/
[3] https://github.com/samsonjs/cookbooks/blob/master/node/attributes/default.rb

So technically we download & compile but it's mostly automated. I
really recommend something like chef or puppet.

-s

[Ryan Gahl]

aha, and now it clicks. Sooo... there ya go Fedor :) 

(you were talking about a slightly higher level problem than what I was thinking about)