Elinks texas health org12/14/2023 One for arm64 (Pi4 and Pi3) and one for all the other arm32. I now that arch=('x86_64' 'aarch64' 'armv6h' 'armv7h')Īnd that usually, if well done, only two binaries are needed. To, not sure if arch=("i686" "x86_64" " xyz arm something " ) So this, "elinks-git", or even a "elinks-bin" could be updated to include arm: Think of Arch Linux 32bit, and their tireless work. So you can run it on the Raspberry Pi or old 32bit computers. It's cool that upstream now even provide binaries for arm and i386. Question about support for arm architectureĢ021. I for one cannot understand why would one even want to hear about javascript in a cli browser. Is this the reason why the official elinks hasnt been updated ? To keep trying to support any kind of buggy incomplete javascript or spidermonkey support ? # (upstream has no interest in writing that)Īnd this, elinks-git PKGBUILD has this difference: 2 -without-lzma \Īnd "felinks-python", even has brotli and zstd support, ĭoes this mean that the Arch official packager "insist" or "hope" for elinks # todo: make it work with a modern 'js' package I noticed this January 2021 comment on the official arch package, I think, if I'm not mistaken, that this is the intent and direction of upstream elinks. Notice the "Disabble spidermonkey" there. include unistd.h and errno.h to define safe_read() #107.alert when moving to the next match of a failed search #101.fix error message when no previous search was performed #100.Show error message about libgcrypt-config.I just noticed that Arch's official is still stuck in the 0.14.0 January 2021 version.īut, upstream, has released 0.14.1 in May 2021 But it doesn't look like the developers think that way: the getelementbyid branch is currently receiving very active development focused on JS support, see (currently ).Ī question about javascript (evil/good ?) to all commenters here.Īrch's official package with their PKGBUILD and CHANGES: I'd welcome it-javascript is a security disaster even for established browsers, and putting it into a small project like a terminal browser is calling for trouble. Get rid once and for all for everything javascript related. I have no experience with autoconf, but to me it looks like the generated scripts in the projects haven't been updated since 2004 and they fail some detection on recent systems. I needed to add a autoreconf -ifv to make it work, which I've also committed to the PKGBUILD. I've added the architectures you suggested. I tested this on a Pi 4 and it seems to run on aarch64-but I only made a quick test with default config. I didn't look through everything though.Įlinks-0.14 compiles fine, so I've switched to that branch for now (currently version 0.14.1). I've compared the 0.14.1 release tarball with the elinks-1.14 branch and couldn't tell if that's where the source comes from, because it looked like a different state of the project. Yes it's been like that on master for a while, and there haven't been any changes to that branch for all that time. I think it's that "infamous" ld linker thingy error again: Git version with Javascript disabled by default. To An advanced and well-established feature-rich text mode web browser. Guarantee that my "elinks-git" wont be able to execute any javascript at all in my computer ?Īnd if that is true, may I suggest that the PKGBUILD description be edited from: An advanced and well-established feature-rich text mode web browser. In case the developer "stuffs" javascript support by default, do these options in the PKGBUILD: -without-spidermonkey \ In that case, what I wanted to make sure is what I'll be getting in the future if I use this, "elinks-git" PKGBUILD. And if so, I assume the official Arch package will just follow that right ? And so the Arch official "elinks" package will support javascript. So, the main developer, rkd77, is still aiming at some sort of javascript support then. Just checked the master, I see JavaScript is currently disabled. I just randomly read this in the repo and assumed it was the project direction. But it doesn't look like the developers think that way For your comment and clarifying things !.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |