Run a Google search for it:
libicudata.so.74 freshports
Run a Google search for it: libicudata.so.74 freshports
# cat /etc/pkg/FreeBSD.conf
FreeBSD: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
#url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
It works!Hello,
to install all the packages that you lost you can change the repository from "quarterly" to "latest"
Yes, it's not so fast.I quit building the missing vscode, it was taking already 3 complete days building it all, electron etc.
So now I will have to live without my favorite dev tool.
They'll be here soon...Losing packages will bring instability or even break the system down.
Yes, this is not so good practice.if you mix ports and packages. Dependency hell is now biting a lot quicker...
Well, when I tried the pre-compiled packages from FreeBSD repos, my experience was no different than with Linux. Upgrading a given package really meant reinstalling the whole system from scratch, it's been that way the entire time for me ever since I discovered Linux in 2003. I moved to FreeBSD in 2017 because I found ZFS attractive, and I stayed because the Ports system offers more flexibility than pre-compiled package repos. So really, this is just a downside of Open Source in general, both in Linux and BSD camps, just nature of the beast.Yes, this is not so good practice.
It's a good excuse!I stayed because the Ports system offers more flexibility than pre-compiled package repos.
It takes a couple days on a Ryzen 5 7600. But for me, the patience is well worth the results. It does take about a week on a Ryzen 5 1400. If you do your planning, some of the compilations can be done overnight while you sleep.But I remember the times when I compiled X11 and KDE and it was pure hell!
As a code editor, this looks interesting... esp. if it dumps dependency on electron. I'm not wild about it depending on Linux libs, though. Straight GTK 3/4 should be plenty, IMHO (not that I have the skill or time to make that happen).
Dang, me seeing this from another people too on the Forums...Couldn't build vscode, it stops with "*** Signal 9" probably not enough memory to build it, 16GB aren't enough... well.
I have to use some other editor meanwhile.
Will the issue only be resolved at the next 'quarterly' branch release in July? I will move to 'latest' if that's the only option to fix the problem, but would prefer not to.Hello,
to install all the packages that you lost you can change the repository from "quarterly" to "latest"
In the past it was my go to text editor but it lacked plugins etc. and once i discovered vs-code i kinda never got back to sublimeAs a code editor, this looks interesting... esp. if it dumps dependency on electron. I'm not wild about it depending on Linux libs, though. Straight GTK 3/4 should be plenty, IMHO (not that I have the skill or time to make that happen).
or you could run code-server.Hello,
about editors/vscode/
"Electron is blacklisted from the package builder. As this is a dependency of the vscode package, this may mean you will have to build VS Code from the ports collection"
[HEADING=1]install.sh[/HEADING]
The easiest way to install code-server is to use our [URL='https://github.com/coder/code-server/blob/main/install.sh']install script[/URL] for Linux, macOS and FreeBSD. The install script [URL='https://coder.com/docs/code-server/install#detection-reference']attempts to use the system package manager[/URL] if possible.