[beports] Re: Port additions

Hi,

Am 22.04.2008 um 19:10 schrieb scott mc:


I'll read over the guidelines later today.  I'm going to try to go
through the roadmap list and try to get previous port info posted for
each item, so if/when someone gets around to it there will be a place
to start from.  Also knowing a contact person who attempted or
succeeded at previous ports might be helpful as well.
http://tools.assembla.com/BePorts/roadmap



I also added a few more port requests in the past few days but marked
them as unscheduled.  Not sure if we want to roll any of those into M1
or not.
Actually I haven't touched tickets since joining BePorts. My take is that the M1 milestone was more dedicated to the legacy Be systems. With a focus shift towards Haiku, we might or might not end up changing this project's name; while Wiki pages would be easy to migrate, I'm not sure about the tickets and would prefer to wait until Brecht has decided on that before changing milestones and adding tickets for things already in the Wiki.
My idea would be to create a new milestone for a self-hosting Haiku and drop the tickets for ports already done by Ingo (but create a Wiki page for each, linking to the patches). 



I still haven't had a chance to get a complete native build system put
together.  I do have one setup on ubuntu but will that work for
attempting ports or are you doing it from within Haiku?
Both is possible. For cross-compiling autoconf-based software I created a simple shell script: 
http://dev.haiku-os.org/ticket/1844
Cross-compiling is faster than compiling under emulation/ virtualization but can be much trickier. 

I'd recommend native development on Haiku for the start.


I told Luc about BePorts as well, he's done ports from ZetaGames and
has had to port supporting libraries in the process.


Sounds great!


I wonder if we should also add in all of the libraries that were part
of the LibPak on bebits?  That hasn't been updated in 3 years or so.
Those are handy to have if you want to play many of the games (and
other programs) posted on BeBits.  Some of them are already part of
Haiku so we could skip those.
In general I'd say we should document "everything" we stumble upon. But of course as there are a lot of pre-Haiku ports, that takes time. I have therefore focused on core tools and libraries and their dependency tree for now. 

Andreas

--
BePorts homepage - http://tools.assembla.com/BePorts
List archives: http://www.freelists.org/archives/beports
Administrative contact: brecht@xxxxxxxxxxx

Other related posts: