Date: Sat, 20 May 2017 08:39:33 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: How should we name node-js ports ? Message-ID: <1f61b3c2-2465-ceba-03ab-2734bd74b37b@FreeBSD.org> In-Reply-To: <210be3b5-35a8-5458-8991-7759f964f8ef@freebsd.org> References: <ba4cd1f6-2bd7-f710-2e6c-56c470c5ef7d@bebik.net> <210be3b5-35a8-5458-8991-7759f964f8ef@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --m37GEvt1qmusJOjOafOgcpwMegMat4K7h Content-Type: multipart/mixed; boundary="CxUtV6Ce3FKmj5MnmIQNCGPCTnFFt32Vn"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Message-ID: <1f61b3c2-2465-ceba-03ab-2734bd74b37b@FreeBSD.org> Subject: Re: How should we name node-js ports ? References: <ba4cd1f6-2bd7-f710-2e6c-56c470c5ef7d@bebik.net> <210be3b5-35a8-5458-8991-7759f964f8ef@freebsd.org> In-Reply-To: <210be3b5-35a8-5458-8991-7759f964f8ef@freebsd.org> --CxUtV6Ce3FKmj5MnmIQNCGPCTnFFt32Vn Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 t= ask. > 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. >=20 > 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 --CxUtV6Ce3FKmj5MnmIQNCGPCTnFFt32Vn-- --m37GEvt1qmusJOjOafOgcpwMegMat4K7h Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZH/K7XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATRvkQAJxWWRROsemqkf7n7tnGF50b jAhz2J12f6IjUARAq1yUfoMKC5p1DWlvdWf47wQ9Wbd1cZex8L4J0aOjm8vjeNZg 3ayzmHqRjVjHIf8FZN2ZPJB31GWbIRjcL3Vr1+H11oo6cpcVudoUXGxZc0VrQuy9 nE6eC5WEce+YLMEUrXnDbBs3pGUc6in3Ko3tJ2LoSxIIoJQxdztC9PVo61cTuGyK 44LoQvaIQKo52279hj3qqetbtCtaw1uz2ObYB9M0mPQUr2J8xjnrdKIUY0CvNiHk BwS6vCoT0gENpUrF99k0JStUTW49nw6irdDdQifNaiEcYbe1JFSKv7ZnxVarrKpN MFWBSWc6FI5EhJQ0Kqu1BdN66/5+2Lp5orK7fU5DqMGhxh0Q9KzGvy/5/Boc9eD2 MRiY0dp/TUY3uiYiO/S2s6W1MFEGWdQuMiwmhqc/AAhOEITlk/0mQfyrQNVCkQzC J8mu0Ftbhf/83MNT0/dQZHG9sI0jxjy2m8B8sc7sVvXEhEwmwVVBoJJSiCjtY4Sk zHBs2iFuWu8xcr4ZzfCHY9sumlEu7IqxvrwdkrDqHzfDkOdSbNQ2uhqziNrLI037 n/RhA/7+/QArYMf+SXzU4v99LLaHbNFb8JZocW4pLYmrSIgC1xWtkHhb9WLQfOE0 isYarpH337hhPdfn/t8b =zjOV -----END PGP SIGNATURE----- --m37GEvt1qmusJOjOafOgcpwMegMat4K7h--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1f61b3c2-2465-ceba-03ab-2734bd74b37b>