Porting Odyssey 1.26 from MorphOS 3.12!

[wawa]

ok. out ot interest:
mkdir AROS-v0
cd AROS-v0
git clone https://github.com/deadw00d/AROS
cd AROS
git checkout alt-abiv0
cd ..
cd..
mkdir aros-v0build
cd aros-v0build
../AROS-v0/AROS/configure --target=linux-i386 --with-portssources=/home/wawa/portssources
make -j4
.....and hope it will build aros i386 abi v0..

[wawa]

Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P   However there's no current news on my hint.

admittedly we all kind of failed to approach this in an orderly manner.
i dont even understand where to find the genuine revision of webkit engine that along with the ppatch still worked on ppc/morphos/os4. are these in kas1e branch?

[wawa]

unpacking gcc-4.6.4 its been a while-..

[ASiegel]

Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P   However there's no current news on my hint.

It was not merely a conversation, but a public commitment to donors. Here is the full quote:

"If this project is successfully funded, and as long as the resulting ports stay true to the original version of the Odyssey Web Browser in terms of user experience and feature sets, Fabien Coeurjoly plans to share all source code that he will develop himself for future versions of Odyssey Web Browser for free."

Source: https://www.power2people.org/projects/odyssey/

Since the bounty project has been completed, no new versions of Odyssey have been released by Fabien and, as I am sure everyone will understand, you simply cannot share code that you never wrote.

[terminills]

Well the original conversation did include keeping all future updates open provided the ports were up to the standards of the original. ;P   However there's no current news on my hint.

It was not merely a conversation, but a public commitment to donors. Here is the full quote:

"If this project is successfully funded, and as long as the resulting ports stay true to the original version of the Odyssey Web Browser in terms of user experience and feature sets, Fabien Coeurjoly plans to share all source code that he will develop himself for future versions of Odyssey Web Browser for free."

Source: https://www.power2people.org/projects/odyssey/

Since the bounty project has been completed, no new versions of Odyssey have been released by Fabien and, as I am sure everyone will understand, you simply cannot share code for browsers that do not exist.

I know the details quite well Andre as I was the one who negotiated the initial opening with Fab(as you may recall I sent you the writeup on
Fri, Nov 1, 2013, 3:53 PM EST.).    I'm just not convinced your timeline is quite correct.

[wawa]

oh my.. build issues coming up, long fixed on abi v1. am i really supposed to start back porting fixes to v0?? considering that pull requests will likely never be accepted?

[ASiegel]

I'm just not convinced your timeline is quite correct.

Well, I stand corrected. The fund raising was completed a short while before the "original" version 1.24 was released by Fabien himself in 2014.

So, "no new version since 2014" would have been more accurate on my part.

[ASiegel]

admittedly we all kind of failed to approach this in an orderly manner.
i dont even understand where to find the genuine revision of webkit engine that along with the ppatch still worked on ppc/morphos/os4. are these in kas1e branch?

Well, is there anything missing from the source archive on Aminet?

[wawa]

lol just a small shock not finding odyssey repo on my github till i remembered i have transferred it to amigaports..

[wawa]

@asiegel
ill look at it, for now i assume kas1e branch is what still works on ppc.. but maybe id be better off asking him.

[deadwood]

my pull request on deadwoods gitub just sits there since a year becoming outdated.

FYI, I added you as a contributor back in February so you should be able to commit those changes directly without need for pull request. I don't have the capacity to review the request, so if  it compiles and generates a working Odyssey build, commit the changes by all means.

[deadwood]

oh my.. build issues coming up, long fixed on abi v1. am i really supposed to start back porting fixes to v0?? considering that pull requests will likely never be accepted?

I have builds set up for V0. If you produce pull requests and ping me about them, I will merge them back to the v0 branch.

[wawa]

@deadwood
ill see what i can do. but i dont want to mess up anything. and you know how capable i am. lack of time is our all problem alas.

[wawa]

i have rerun an attempt to build abi v0 in a different vm and it looks like it built. perhaps there was just one issue after all. how do i verify this is v0 though?
now considering odyssey it might be possible to stick to icu 4.2.1 but i might run into issues building 60.2 if it was necessary. i though think it was only needed for other targets as i386.

[wawa]

yeah, its abi v0 for sure. just verified. even folder structure is different a bit.
now. to build odyssey with the build sys i need some modules from contrib. though im not sure if the sources are still fully compatible with v0. especially the mmakefiles.
@deadwood
what do you think? you aint hosting contrib back port by chance if it was necessary?