[openbeos] Re: [haiku-development] Coordinating ports (#2) (was: Re: Distributed Version Control Tools)
- From: "Jorge G. Mare (aka Koki)" <koki@xxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 21 Apr 2008 14:55:36 -0700
François,
This looks like a great summary.
May I suggest that you put it into a document on the website, so that we
can link to it from the development page? ;)
Cheers,
Koki
François Revol wrote:
>>> Just FYI, to prevent any other unnecessary work duplication.
>>>
>> Better than just announcing finished ports, the real way of avoiding
>> duplicated work would be to announce the beginnings of a port.
>>
>
> I've seen numerous stuff re-ported after I already did as well...
> sometimes I didn't have time to publish diffs, but...
>
>
>> That was the whole point that this list pointed me to the BePorts
>> project. I have since then updated large parts of the site, logging
>> pretty much everything I have done so far and publishing my patches
>> in
>> its SVN. Other than that I'm only aware of Ingo's ports in Haiku's
>> SVN, of Ryan's WebKit port and the OpenJDK port.
>>
>> Only recently did I learn that Duane had been porting Python and just
>> now that Niels has ported git, too.
>>
>
> I'm quite sure they didn't even read my zeta python diffs...
> Parts probably don't apply anymore, but it's always easier to have
> hints.
>
>
>> We really need a way to coordinate such efforts!
>>
>>
>
> Sure, but first...
>
> a-1)
>
> Make sure you check known sources:
> - ftp.be.com and geekgadgets mirrors, they often contain old versions
> of things.
> - http://revolf.free.fr/beos/patches/
> and the old archive at
> http://web.archive.org/web/*/clapcrest.free.fr/revol/beos/patches/*
> though I tried to put all relevant on the new place.
> - http://beclan.org/ there is a "bepatched" project that prefigured
> BePorts (hmm svn seems empty ? used to work).
> - http://developer.berlios.de/search/ for "beos" and "haiku", there is
> a wxWidgets and OCaml beos port...
> - osdrawer.net of course
> - sourceforce.net and .jp sometimes have unadvertised ports...
> - the mailing list(s!) for the project you want to port, they often
> refer to old proposed diffs for BeOS ports as well. (I sent several
> times my XEmacs diffs on xemacs-devel as work in progress.)
> - check if there is a BeOS maintainer (I'm the one for ffmpeg) as he
> probably started porting to Haiku or at least knows what must be done.
>
>
>> a) When someone starts a port, please announce it, so that a Wiki
>> page
>> on BePorts can be set up, linking to external pages or tracking
>> progress/patches there. This could be on the BePorts mailing list or
>> on the OpenBeOS mailing list (since usually it's not directly related
>> to Haiku development).
>> //www.freelists.org/list/openbeos
>> //www.freelists.org/list/beports
>> Or simply drop me or Brecht or Scott a line.
>>
>
> Just to avoid dup work again let me list what I have around...
> Currently all are BeOS only ports, hopefully I'll soon have a dev env
> setup in Haiku. Most of them I regularily svn/cvs up to keep them
> building at least.
> Those marked (D) have diffs at http://revolf.free.fr/beos/patches/ (but
> likely not the latest)
>
> - XEmacs (BeOS port, doesn't work on Haiku due to vm split change,
> dumping it directly KDLs for now) (D)
> - ffmpeg (I have some BeOS fixes locally that are not accepted in svn)
> - libusb (slaad almost finished by port, ask him on IRC)
> - links (D)
> - openvpn (reminds me I should port my tun/tap driver to Haiku) (D)
> - OpenSound of course (D)
> - SANE (BeOS, I started fixing cvs HEAD as they broke the build)
> - TCL/TK (BeOS, started native gui)
> - zsh (BeOS)
> - IM Kit (some fixes) (D)
> - bash_completion (lots of BeOS-specifics, was in Zeta)
> - CMU Sphinx (BeOS long ago) (D)
>
> I have some old diffs of fixes for things like bind, BZFlag, qemu,
> attempts on samba, tcsh, UnderC... so make sure you check them.
>
> I'll try to update those for Haiku and push them to BePorts but I don't
> have any ETA.
>
> François.
>
>
>
Other related posts:
