On Wed, Jul 09, 2014 at 03:56:36AM -0700, Vasily Mikhaylichenko wrote:
> Taking a step back, isn't the ultimate goal just making all the
> important modules installable on OpenBSD from npm?
My goal is to allow people who are not node developers to install
programs written in node with `pkg_add`, such as the keybase
command-line tool.
It seems that your goal should already be reachable. The only
exceptions should be things requiring patches to work on OpenBSD.
Unless I am misunderstanding, which is possible as I have little
experience with node, but the few things I have installed with `npm
install` just worked.
On Wed, Jul 09, 2014 at 10:57:30AM +0000, Alexey Suslikov wrote:
> Andrew Fresh <andrew <at> afresh1.com> writes:
>
> > The biggest problem is that this makes patching dependencies difficult,
> > that is, if multiple node apps depend on node-pg, while we needed
> > patches for it, those patches would have been hard to handle
> > automatically.
>
> maintenance resource was a main issue to not follow this way.
> it was discussed with abieber@ some time ago, and decided to
> only port if module needs to compile something (native binding
> for instane, like node-pg).
Was this discussion on the mailing list someplace? I didn't see it with
a quick search of the archive.
> in production, every application I use has an install goo which do
> all necessary work including local module installation via npm.
So you use npm for your production node needs rather than OpenBSD's pkg
tools?
> it's fine. taking fast versioning of some node mudules in account,
> I'd better concentrate on development, not port maintenance.
While I mostly agree, I really like to get my laptop back into a running
state with little more than `pkg_add -z -l pkg_info_manual` and that
doesn't work if I install things with npm directly.
> please, don't touch it :)
How does putting things in ports break your use?
Perhaps the best approach is a hybrid, as you say, port things that need
compilation or patches and then let everything else install as part of
the port. I will see if I can figure out at least putting them into
${DISTFILES} so that if a lib is ported, finding ports that need depends
added should be fairly straight forward.
