FreeLists / beports / [beports] Re: Port additions

[Brecht Machiels <brecht@xxxxxxxxxxx>]

Hello,

On Tue, 2008-04-22 at 20:18 +0200, Andreas Färber wrote:
> 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.

The M1 milestone is IMO applicable to Haiku too. I think we should focus
first on porting the most common software packages first. This is
however hard to define. I tend to mostly think of development tools
(compilers, subversion, autotools, ...) and very commonly used libs
(glib, readline, curses, ...).

Creating a backup of the Trac site includes everything, AFAIK. Tickets
and milestones are included.

About renaming BePorts to HaikuPorts...
I have changed the Trac title to 'HaikuPorts'. We can start changing the
name BePort(s) to HaikuPort(s) on all wiki pages. I opt not to move
everything over to a new Assembla space just yet, as I'm looking into
writing a Trac plugin to enforce the PortLog markup, and I'm not sure if
we can use custom plugins on Assembla. We might have to move to a
different server. Also, I stumbled upon a Trac plugin that could
automatically list all wikipages under 'dev-lang' for example (that's
how I understood anyway). That would come in handy too.

> 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).

That seems like a good idea. This probably should have a higher priority
than the current M1. It would actually be a subset of M1.

> > 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.

Perhaps it's a good idea to have a tutorial on BePorts on how to set up
a native development environment on Haiku. That is, if it isn't already
documented somewhere.

Regards,
Brecht


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