Re: How should we name node-js ports ?
On 20/05/2017 07:56, Julian Elischer wrote: > this brings up the whole question of whether we should package these > things ourselves anyhow. > python and perl have their own schemes (pip et al.) and with npm (and > others) node is no exception. > it seems that to chase these packages down manually is a never ending task. > maybe the way we should handle it is to have a generic "handover to > external package manager" feature, > so that we somehow let npm (or whatever) do it ting but then take the > output result an put it into our database. > > At $JOB we have the issue of many many node modules for our new gen UI > and it causes us a great headache. Certainly with perl, python, ruby, php and the like there is the problem of when the perl or whatever module depends on some external library. The native package managers for those languages really don't handle those sort of dependencies at all, other than documenting that library 'foo' should be installed. Not sure if node or go or whatever have the same sort of out-of-context requirements. Currently the only way to handle the dependencies on external libraries is to create a port. We'd have to do something along those lines in any case as the upstream are unlikely to include FreeBSD specific dependency information in their software. I also like the idea of having the package database record all of the files installed by any package manager -- that requires a FreeBSD specific patch for each of the various languages, which is a lot of work but must be cheaper overall than attempting to create a port for every possible perl module or ruby gem and so forth. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: How should we name node-js ports ?
On 14/5/17 8:16 pm, Rodrigo Osorio wrote: Hi, I have a bunch of nodejs ports to add, most of them as dependencies, and I wonder if we can find a naming standard like adding 'node' or 'node-js' prefix in the name ; I personally prefer 'node'. As a result a port who install the node package xxx will be named 'node-xxx' Does it sounds good to you ? Thanks for your time, this brings up the whole question of whether we should package these things ourselves anyhow. python and perl have their own schemes (pip et al.) and with npm (and others) node is no exception. it seems that to chase these packages down manually is a never ending task. maybe the way we should handle it is to have a generic "handover to external package manager" feature, so that we somehow let npm (or whatever) do it ting but then take the output result an put it into our database. At $JOB we have the issue of many many node modules for our new gen UI and it causes us a great headache. -- rodrigo ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How should we name node-js ports ?
> On 15 May 2017, at 20:22, Rodrigo Osorio wrote: > > > Hi Adam, > > Thanks for your feedback. > > On 05/15/17 18:52, Adam Weinberger wrote: >>> On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov wrote: >>> >>> >>> npm packages can be installed by yarn as well; nodejs is really the common >>> name and makes a better prefix. >>> >>> That said, making node ports does not sit well with me. npm/yarn manages >>> node packages. Things will break if a user has those same packages >>> installed globally and tries to update or remove them, or if a user needs >>> specific global versions installed. I agree with this sentiment. It also does not sit well with me to use one package manager (pkg) to run another package manager (npm) to install dependencies. In my expereince, Node.js apps tend to have their dependencies installed locally, as it is too easy to get into conflicts or incompatibilities with globally installed versions. The exception to the rule is for things that install a runnable command, like grunt-cli, npm, mocha, and so on. >>> Rodrigo, I think your better option is simply to bundle those dependencies >>> yourself, at the specific versions that your port requires, and install >>> them to a private location. > I decide to split the dependencies in several packages and I use npm a short > perform the package installation before > the staging. That way node packages remains available to other and can be > reused as dependencies for others node ports. Like expressed above, I think the "remains available to other and can be reused as dependencies for others" can be more harmful than helpful. -- Bradley T. Hughes bradleythug...@fastmail.fm ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How should we name node-js ports ?
On 05/15/17 14:57, Ruslan Makhmatkhanov wrote: Rodrigo Osorio wrote on 05/14/2017 15:16: Hi, I have a bunch of nodejs ports to add, most of them as dependencies, and I wonder if we can find a naming standard like adding 'node' or 'node-js' prefix in the name ; I personally prefer 'node'. As a result a port who install the node package xxx will be named 'node-xxx' Does it sounds good to you ? Thanks for your time, -- rodrigo Am I right they will be actually installed with npm? If so, it would make sense to name them npm-, like rubygems installed packages. Hi Ruslan, That sounds good to me, if everyone agrees we can move this way. -- rodrigo ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How should we name node-js ports ?
Hi Adam, Thanks for your feedback. On 05/15/17 18:52, Adam Weinberger wrote: On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov wrote: npm packages can be installed by yarn as well; nodejs is really the common name and makes a better prefix. That said, making node ports does not sit well with me. npm/yarn manages node packages. Things will break if a user has those same packages installed globally and tries to update or remove them, or if a user needs specific global versions installed. Rodrigo, I think your better option is simply to bundle those dependencies yourself, at the specific versions that your port requires, and install them to a private location. I decide to split the dependencies in several packages and I use npm a short perform the package installation before the staging. That way node packages remains available to other and can be reused as dependencies for others node ports. # Adam ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How should we name node-js ports ?
> On 15 May, 2017, at 6:57, Ruslan Makhmatkhanov wrote: > > Rodrigo Osorio wrote on 05/14/2017 15:16: >> Hi, >> I have a bunch of nodejs ports to add, most of them as dependencies, >> and I wonder if we can find a naming standard like adding 'node' or >> 'node-js' prefix in the name ; I personally prefer 'node'. >> As a result a port who install the node package xxx will be named 'node-xxx' >> Does it sounds good to you ? >> Thanks for your time, >> -- rodrigo > > Am I right they will be actually installed with npm? If so, it would make > sense to name them npm-, like rubygems installed packages. npm packages can be installed by yarn as well; nodejs is really the common name and makes a better prefix. That said, making node ports does not sit well with me. npm/yarn manages node packages. Things will break if a user has those same packages installed globally and tries to update or remove them, or if a user needs specific global versions installed. Rodrigo, I think your better option is simply to bundle those dependencies yourself, at the specific versions that your port requires, and install them to a private location. # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How should we name node-js ports ?
[Default] On Sun, 14 May 2017 14:16:23 +0200, Rodrigo Osorio wrote: >Hi, > >I have a bunch of nodejs ports to add, most of them as dependencies, >and I wonder if we can find a naming standard like adding 'node' or >'node-js' prefix in the name ; I personally prefer 'node'. > >As a result a port who install the node package xxx will be named 'node-xxx' > >Does it sounds good to you ? Since "node" already has a well-established general meaning that has no immediate connection to software, it'd be much less confusing to use "nodejs", since that *does* have a direct and immediate connection to the software ports you plan to add. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How should we name node-js ports ?
Rodrigo Osorio wrote on 05/14/2017 15:16: Hi, I have a bunch of nodejs ports to add, most of them as dependencies, and I wonder if we can find a naming standard like adding 'node' or 'node-js' prefix in the name ; I personally prefer 'node'. As a result a port who install the node package xxx will be named 'node-xxx' Does it sounds good to you ? Thanks for your time, -- rodrigo Am I right they will be actually installed with npm? If so, it would make sense to name them npm-, like rubygems installed packages. -- Regards, Ruslan T.O.S. Of Reality ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
