I wanted to ask this since some time but forgot about it always. There is a Guest Addons package in the repository which after the comments located there is supposed to be used “inside” haiku running as guest. From what I see everything segfaults when run so I conclude guest addons are not working in haikue. Have they ever worked and more importantly is it planed to get them working again? If not they should be removed from repositories.
In the same vein, lyx is available on x86_64, but texlive is not. If there is a problem with porting texlive, then perhaps lyx should be pulled until that is done. It just confuses new users.
I’ll try to add x86_64 support to texlive port.
I guess users should be informed that posting issue on haikuports github project page is the best way to change things.
Regarding VB guest additions, I dunno but being using VirtualBox myself under x86_64, I may give a look one day.
Texlive isn’t a requirement for LyX, so what’s the problem?
VB guest additions compiles under x86_64 but when installed vbox drivers aren’t get loaded. See this commit for details: https://github.com/haikuports/haikuports/commit/befb49f5683a3c1c5dc31eebe2b75f6ae47225df#diff-ebc27920c07cdec9acf0f26f637eb7d4
Could you expand on that? vbox guest additions only work on x86_gcc2 atm.
That is an error in the LyX package. It installs without a TeX installation, yes, but try to do anything with it that way and watch the error messages come thick and fast. Save As? Missing utility. Insert graphic? Missing utility. And all those utilities are in Texlive.
https://yahbblog.wordpress.com/2017/05/21/a-solution-to-haikus-word-processor-woes/
Well, things could be better. Last time I tried I could save a lyx file, and insert a png image. I did receive a warning message (not an error message). Texlive 2014 recipe produces a monolithic package of around 800MB, it should probably be split up before adding it as a dependency. Issue created: https://github.com/haikuports/haikuports/issues/1767
This is x86_64 version of guest additions which you downloaded from the testing repo (http://eu.hpkg.haiku-os.org/haikuports/master/repository/x86_64/current/packages/) that includes juts about everything that builds no matter if it actually works or not, that’s why you won’t find it in the official repo. As I said only x86_gcc2 version of guest additions currently work.
Then somebody should clear out the nightly haiku repository. It can’t be you tell people to use nightly (and I did not install any obscure repositories, just the official ones) and then deliver packages to them which are not working. It’s find with me if it doesn’t but that’s a bad situation to be in.
This package is not in nightly haiku repository. It is in testing repository which can contain broken packages.
If you experimented with different repos in the past, and switched back to the official ones, you can try to use “pkgman full-sync”, which will (in addition to what “update” does) allow to remove or downgrade packages to match what is in the repos.
I ensured now HaikuPorts is not in the repository list (which doesn’t make sense to me, it’s claimed you need HaikuPorts to get nightly). I ran “pkgman full-sync”. VBoxAddons are not removed and still segfaults. From this I conclude it’s broken in Haiku master reporsitory (since you claim full-sync downgrade packages to repository version).
It was suggested to remove the HaikuPorts repository, but to make sure you have the official HaikuPorts repo (e.g. http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/current ) added, not the experimetal repo (e.g. http://eu.hpkg.haiku-os.org/haikuports/master/repository/x86_gcc2/current ).
In any case, even the official one has vbox additions packages:
32bit:virtualbox_guest_additions-5.1.26-1
64bit virtualbox_guest_additions-4.3.53_svn-7
Which of those doesn’t work for you?
I’ve got now only one repository: “http://packages.haiku-os.org/haiku/master/x86_64/current” . I never used “eu.hpkg.*”.
The version causing segfaults is 5.1.26-1 . You claim it’s “32-bit”. That doesn’t make sense since I use 64-bit. A wrong package in the 64-bit repository?
No. Just a typo on my part.
korli just removed the offending package from the 64bit repo. Thanks korli!