View previous topic :: View next topic |
Author |
Message |
Garbanzo n00b
Joined: 06 Aug 2018 Posts: 37
|
Posted: Fri Sep 13, 2019 6:35 am Post subject: Good way to install typescript? |
|
|
What's a good way to install typescript? Usually it's done with: Code: | npm install -g typescript |
Obviously portage wont know about it, but is it safe since nothing in the tree should depend on it? |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30965 Location: here
|
Posted: Fri Sep 13, 2019 6:43 am Post subject: |
|
|
It's not recommended to global install anything outside portage.
Better way is install it only for your user or try jm-overlay overlay that as this package _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Garbanzo n00b
Joined: 06 Aug 2018 Posts: 37
|
Posted: Sat Sep 14, 2019 7:33 am Post subject: |
|
|
Thx. I did use the overlay.
What kind of trouble would global installs with npm cause? npm has lots of little package which won't all have ebuilds (like 'is-odd' which only checks if a number is odd). If nothing else depends on it would it be safe? |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21724
|
Posted: Sat Sep 14, 2019 4:52 pm Post subject: |
|
|
Portage assumes that all relevant system-wide files are known to it, by way of installing them through it (or a compatible tool that would also register the files in the package database). Further, it assumes that files it installed were not silently changed by other programs. If you install an npm package system-wide, you risk three things:- It installs a file that Portage is not expecting, which may lead to spurious dependency problems later.
- It overwrites a file managed by Portage.
- It is not managed by Portage, so future upgrades/removals are your responsibility, not Portage's responsibility.
If you are willing to deal with those risks, yes, go ahead. |
|
Back to top |
|
|
|