From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.oboj.net ([195.178.185.14]) by ewsd; Fri Jan 24 13:40:36 EST 2020 Received: from localhost (localhost [127.0.0.1]) by mail.oboj.net (Postfix) with ESMTP id 177CABF16A7 for <9front@9front.org>; Fri, 24 Jan 2020 19:40:29 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mail.oboj.net Received: from mail.oboj.net ([127.0.0.1]) by localhost (mail.oboj.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gJuyP9WJMtBR for <9front@9front.org>; Fri, 24 Jan 2020 19:40:28 +0100 (CET) Received: from www.oboj.net (unknown [195.178.185.23]) by mail.oboj.net (Postfix) with ESMTP id 5CC70BF16A4 for <9front@9front.org>; Fri, 24 Jan 2020 19:40:28 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 24 Jan 2020 20:40:28 +0200 From: jamos@oboj.net To: 9front@9front.org Subject: Re: [9front] Netsurf 3.9 for Plan 9 (work in progress) In-Reply-To: <41F6539D-D7DF-4799-BDA0-A4D1CE5E9C56@sdf.org> References: <7EA616C7FF07CA423F342D0FFDF55539@eigenstate.org> <0d0c66a3d67f051752a3d82ea1190304@oboj.net> <9BF8795F-C61C-402C-99AB-1E53D9CE91B3@sdf.org> <41F6539D-D7DF-4799-BDA0-A4D1CE5E9C56@sdf.org> Message-ID: X-Sender: jamos@oboj.net User-Agent: Roundcube Webmail/1.3.4 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: shared agile HTTP over ORM extension configuration controller I just committed the first changes to the git repo that Ori kindly set up for the Plan 9 port of Netsurf. I have checked in the files for the smallest and simplest library (libwapcaplet) as a test, using git9 by Ori. I will continue with the other libraries, and the browser itself. Each library is in it's own repo on Github. I'll write again when I managed to commit the rest. For the curious, you can help me to see if I did everything correctly, by checking out and compiling the 'libwapcaplet' library. This is my first real Git experience :-) git/clone git://github.com/netsurf-plan9/libwapcaplet.git Kyle> I have something partially working with webfs This is super cool! If you feel for it, it would be interesting to read about your efforts and the problems you encountered. /Jonas On 2020-01-24 20:16, Kyle Nusbaum wrote: > I am away from home for the next week and didn't bring the code with > me. > > I have been hacking on it in my spare time and made some progress. It's > not pretty yet, but it's actually minimally useful (to me at least). I > will try to get some repos set up on GitHub when I get back if someone > wants to look at what I've done. > > On January 24, 2020 3:09:57 AM EST, Eli Cohen > wrote: bump. did anyone ever put repositories of this up yet? don't let > them > shout you down > > On Tue, Jan 7, 2020 at 8:26 PM Kyle Nusbaum wrote: > Attachment didn't take. My mistake. > > On January 7, 2020 10:23:40 PM CST, Kyle Nusbaum > wrote: I gave up trying talking directly on /net/tcp. It is a pointless > exercise and would need to be replaced right away anyway. > > I have something partially working with webfs. I replaced the llcache >> implementation with one that uses webfs. We still need the old version >> to handle objects like "resources:quirks.css" etc. >> >> I'll keep working on it when I get time. >> I'm attaching a screenshot of the thing partially rendering the netsurf > website. > > On January 4, 2020 3:33:48 PM CST, jamos@oboj.net wrote: On 2020-01-04 > 19:14, ori@eigenstate.org wrote: > > What I'd do is clone the upstream netsurf repos onto any git host > that you feel like (except gitlab -- git9 triggers a bug in their > backend, and I haven't had time to find a workaround), and then > branch off a 'plan9' branch that we can work on, and commit the > current state. > That sounds like a cool way, but I am kind of a git rookie. I assume > that the reason to clone the main repository is that it will be easier > to merge them together eventually? Or even to keep the plan 9 branch > up > to date with new versions of the mainline? I have based my port on the > stable release 3.9 while the core team is happily hacking away on what > even will be the next release (usually one version per year). > > The official site has many git repositories > (https://source.netsurf-browser.org) - from which I actually downloaded > every support library separately. Each repository has a tag for each > release. There are also a number of branches (especially for the main > netsurf repository: > https://source.netsurf-browser.org/netsurf.git/refs/heads) that looks > like experiments. > > I might be inclined to keep it simple to begin with, but if there are > very compelling reasons for a more elaborate way, I might be open to > that, in order to avoid lots of work later on. > -- Kyle -- Kyle -- Kyle